structure as a git submodule

Question

structure as a git submodule

Closed this issue 12 years ago · 12 comments

The current structure of the project made it uneasy (for me) to pull it as as working .git submodule of my .pentadactyl main repo. The issue is that the *.penta files are not copied in the main color subdir, so are not found at startup. I tried to modify the runtimepath variable, with no effect. Is there an easy way ? I have just symlink the files, this works, but is not very elegant.

Answer 1 · 2012-09-30T12:25:14.000Z

What would the structure have to look like for this to work?

Answer 2 · 2012-09-30T12:53:32.000Z

I am not sure. For comparison I just pulled
git://github.com/gwash/tab-groups-manager.git in my
.pentadactyl/plugins directory and it worked out of the box.
For some reason if I do the same with
git://github.com/claytron/pentadactyl-solarized.git
in .pentadactyl/colors, it doesn't work.

Answer 3 · 2012-09-30T14:53:09.000Z

The difference is that the tab-groups-manager plugin .js file is at the root, where I've put the .penta files into a sub-directory.

I've not used git submodules much, how does this work with multiple plugins? If they all had a README.md like mine, wouldn't there be some sort of conflict?

Answer 4 · 2012-09-30T19:20:26.000Z

@choufleur do you mean you're doing git submodule add git://github.com/claytron/pentadactyl-solarized.git colors/ ? If so then you're doing it wrong. I would advise you do something along the lines of: git submodule add git://github.com/claytron/pentadactyl-solarized.git colors/solarized ; cd .pentadactyl/colors/ ; ln -s solarized/colors/* ./

That will create symbolic links to the colorschemes. Also if you're making submodules for other plugins, you'll have trouble when you want to use more than one. Someone should probably make a pathogen/vundle equivalent for pentadactyl.

Answer 5 · 2012-10-01T10:50:24.000Z

Thanks. I first did it "wrong" and then "right", as I mentioned in my initial message. I was in fact wondering if a solution better that symlinking does exist. I think you are right about the need of a pathogen for pentadactyl. My issue, tough, is not related to the use of multiple submodules, it already occurs if you want to install pentadactyl-solarized as a submodule, even if no other submodule does exist.

Answer 6 · 2012-10-01T13:11:07.000Z

Are you doing it from the root of your git repository, i.e., if your structure looks like this:

$HOME/
$HOME/.pentadactyl/
$HOME/.pentadactyl/.git
$HOME/.pentadactyl/{colors,info,&c.}

You're at $HOME/.pentadactyl/. I assume you are, but that has caught me more than once.

Answer 7 · 2012-10-03T13:16:12.000Z

Yes, I was at the root, this is not the issue I think. Thanks for your help anyway.

Answer 8 · 2012-10-03T13:44:21.000Z

Yeah, sorry, just trying to cover all bases. I'll try it out myself.

Answer 9 · 2012-11-02T01:40:13.000Z

I've not had a chance to try this out at all. Did you have any luck @sigmavirus24 ?

Answer 10 · 2012-11-02T11:23:32.000Z

@claytron : this works fine by symlinking as described above, so you can close this issue, if you want. In fact it is more pentadactyl related.

Answer 11 · 2012-11-02T13:08:16.000Z

Closing this. We will wait patiently for someone to implement pathogen for Pentadactyl. 😜

Answer 12 · 2012-11-05T17:15:09.000Z

Sorry, I never did try and was without power from a week ago until last evening. But yeah @choufleur is correct. Symlinking works fine.