-
-
Notifications
You must be signed in to change notification settings - Fork 274
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
Consider repos which already have build recipes #7
Comments
This is a great idea -- if nothing else, I have a couple packages that I maintain, and I"ve been struggling with where to maintain the recipe -- in the repo of the package itself is the obvious way to do it. I agree that git submodules are horrible -- is there really no other way? Maybe a meta-recipe that bootstraps conda-build, and then pulls everything from the downloaded repo? I'd have to poke in more to see if that's possible. And it would still require SOMETHING outside the primary repo that would need maintaining... |
Yes. The only problem with recipes inside the repo is that they with by necessity be getting their source from a relative location, whereas a recipe from outside the repo will be pointing to an absolute location. We can mitigate this by requesting the recipe has the ability to switch source based on either some environment variable, or by a tool which automatically adjusts the recipe for us. The Its a bit early in the morning, so hopefully that made some sense. 😄 |
Another detail worth keeping in mind: recipes in the repo can't include the checksum. I have been suing this approach on my projects: the recipe in the repo tagets |
Much more eloquently put @danielballan - thank you! |
Is this still a problem worth solving? It seems we have moved away from using recipes in repos for quite sensible reasons well outlined by @danielballan. Namely recipes in repos are there to be useful for development primarily and possibly releases. Whereas recipes here are for releases only. |
* change text in frontpage * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Some repos ship with a conda recipe as part of the source - it would be nice to avoid duplicating the recipe, and just use that directly - perhaps using git submodules (which are horrible, but would work for this process). Updating a recipe would then be a matter of updating the submodule location.
I did something similar in https://github.com/pelson/package_with_continuous_delivery/tree/_build.
This might also give us a way to package packages for which no recipe is needed (because the
conda skeleton
approach works).The text was updated successfully, but these errors were encountered: