Plugins on GitHub should have one fewer levels of directory structure

[obra]

Right now, to "git co" a plugin into IdnoPlugins, I need to check it out elsewhere and ln -s it to get the "right" directory into the IdnoPlugins directory. If the content of the plugins were lifted up one level, the deploy-from-git process would be a lot easier.

[benwerd]

That's true - I wasn't thinking about the deploy-from-git process as much as the upload-from-zip process. You could always pull the partial git tree though?

[obra]

On Thu, Jul 04, 2013 at 05:56:17PM -0700, Ben Werdmuller wrote:

That's true - I wasn't thinking about the deploy-from-git process as much as the upload-from-zip process. You could always pull the partial git tree though?

I didn't think that worked. But I haven't poked in a long itme.

One reason to think about the "deploy from git" version of the process is how much easier it makes upgrades and updates.

[benwerd]

Agree completely. I'll take a hard look at this a little later on today.

[demisflanagan]

I ran into the same issue and just moved the directory down the tree. It probably broke the git structure but it worked. It would be great if they cloned directly into the plugin directory.

[benwerd]

Marking this as todo this weekend.

[mapkyca]

Ditto.

Current directory structure makes deployment a nightmare.

[benwerd]

Sorry for the delay, folks. This has been a low-idno month, but September will see development ramp right back up. I intend to get to this then.

[mapkyca]

For others in the same position reading this; Git will store symlinks in the repo (providing your OS supports it), so for deploy, create a separate directory and do your submodule checkouts into those, then symlink from IdnoPlugins.

This'll work providing plugins don't make assumptions based on location (which they shouldn't)

[Phyks]

This would be a really great improvement of the plugin system imo :)

[benwerd]

This was completed ... ooh, well over a year ago. Closed! :)