On 7/22/06, André Detsch <[EMAIL PROTECTED]> wrote:
[CheckDependencies exists and works]

Great. :)

So, if we are going to change dependencies code, it's probably time to
integrate CheckDependencies to the scripts. It already represents a
central point of decision making about dependencies. Btw, spending
time on it only after 013 release would be a good idea. ChrootCompile
is allowing us to prepare better Depencies sets. Btw,

I only got a bit confused in this final bit. Do you think it's time to
integrate it or should we leave it for after 013?

there are some issues still open:
For example: on many cases, the Dependencies rules for a Recipe is not
always equal to the Dependencies rules for the compiled package. For
exemple, a given package can be compiled with Glibc [2.3.2,), but,
once compiled on a system with Glibc 2.4, the dependency of the
compiled package becomes Glibc [2.4,) or something like that.

Yes, in the end every package needs to have its dependencies manually
checked. I have outlined some thoughts about this in previous posts
(generated BuildInformation file vs. various *Dependencies files,
etc)... I don't remember the details right now, we need to review that
when we get to implement it.

Hisham: I think it is ok to commit the changes you made you feel
comfortable about them. Personally, I fear to touch the current logic
because of unexpected side effects. The current logic has many flaws,
as you pointed, but there are many 'holes' at the recipes / packages
versions available.  So, I guess I'm neutral about commiting the
changes now ;)

Yeah, I do, because they actually make it stricter, so the side
effects are probably making Compile more annoying when recipes are
half-broken (which is not entirely a bad thing). And like you said,
things are tending to improve in this department.

So, okay, I'm committing my changes.

-- Hisham
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel

Reply via email to