[gobolinux-users] packages not automatically depending on recipe_type?

[Lucas C. Villa Real]

On 2/11/07, Erick Tryzelaar <erickt at dslextreme.com> wrote:
> Hello,
>
> Looking through Compile, it looks like a package with a recipe_type of,
> say, "scons" doesn't automatically depend on scons  and python
> ultimately being installed. Is there a particular reason why this is the
> case?
>
> Also along the lines of package dependencies, I'm coming from a redhat /
> macports world, and there's some other things that could also be nice,
> but I can't find any reference to in the mailing list. First, I don't
> see support for a separate Build Dependencies (such as needing scons)
> that you don't need if just doing a PackageInstall.

We have added recently a file named BuildDependencies which lists
exactly that. If you find wrong dependencies for a given recipe, just
tell us, preferably in the gobolinux-recipes list, and we'll provide a
quick fix for it.

> Second, I also
> didn't see a way to do things like rpm's Provides and Conflicts. Did I
> miss the discussion? "Conflicts" I think would be pretty simple to
> provide as it would just be the same code as seeing if a dependency is
> already installed, then failing if it is.
>
> "Provides" would be much more
> tricky without a database of some sort. But both are really useful in
> long term maintenance and evolution of a package library. Would there
> ever be plans to add something like this?

I'll leave this question to others, as I don't have a point on this.

-- 
Lucas
powered by /dev/dsp