> Yeah, makes sense. It would just be nice to have all the files related to a > plugin in a single directory - it's easy to forget something needs an update > when it's located at a completely different place.
Well in GP itself, all the files to be updated would be in a single subdir, like `build/foo-plugin`. If you wanted to change more than GP's build system files, you would have to send a patch upstream, which is part of the point of this PR. > but wouldn't it be possible to have a separate subdirectory for the > geany-extra files within the submodule tree and .gitignore it in the submodule I don't think it's possible to .gitignore stuff in the submodule and not in the parent repo since .gitignore is always read and is recursive. Moreover, it imposes requirements on upstream, which may or may not have the same GP maintainer as upstream (see GeanyPy, until recently). That said, I don't think it's unreasonable to push some boilerplate build stuff (which doesn't conflict with own build system) to the external plugin, to "register" itself with GP's build system. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/pull/440#issuecomment-225373801
