-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Packages in a subdirectory of a repository #120
Comments
Isn't the "path" option described under "Common options" in the readme what you need? It would look like this: Though I would suggest to use an absolute path with path=${buildout:directory}/python |
The documentation says path is specifies where to make a checkout/clone. What I need is to specify the path inside the repository which is used by buildout to find package sources. |
Ah, you have several packages in the same repo, I misunderstood that. Try this: Supporting it directly would be pretty complicated. If you would specify different branches, but the same repository we wouldn't be able to share the repo and would need multiple checkouts etc. Actually if that's fine, then being able to specify the package root would be useful for some repositories. |
Not quite: I have a single package in the repository, but it is not located at the root of the repository. The directory structure looks a bit like this:
When checking this out buildout needs to be pointed to [sources]
repo = git [email protected]:path/repo.git egg=false
my.package = fs my.package path=${buildout:directory}/src/repo/app which is not as simple or intuitive as the |
I think a better name for that would be |
One package per checkout is all I need :) |
Or actually just |
I noticed that the solution provided by fschulze fails the first time you run buildout with the following message:
An ugly solution to this problem is to run |
I have a couple of packages that are located in a subdirectory of a repository. This makes it impossible to use them with mr.developer. To support this I suggest adding a
source_path
option, to be used like this:The text was updated successfully, but these errors were encountered: