But I think it's a worthless warning for the average user. As long as the depends is met who cares if the others aren't in the 10.3 tree yet or what ever. But of course that is my opinion and I'm not a project lead, but I think that is more devel info if anything.
---
TS
http://southofheaven.org
Chaos is the beginning and end, try dealing with the rest.
On 16-Dec-03, at 9:47 AM, David R. Morrison wrote:
"Justin F. Hallett" <[EMAIL PROTECTED]> wrote:
Modified Files:
ChangeLog PkgVersion.pm
Log Message:
Now we can have longer depends lines for future or missing versions, ie -ssl or nox variants or perl 582 stuff
Index: ChangeLog =================================================================== RCS file: /cvsroot/fink/fink/perlmod/Fink/ChangeLog,v retrieving revision 1.465 retrieving revision 1.466 diff -u -d -r1.465 -r1.466 --- ChangeLog 15 Dec 2003 11:01:54 -0000 1.465 +++ ChangeLog 15 Dec 2003 23:31:00 -0000 1.466 @@ -1,3 +1,8 @@ +2003-12-15 Justin F. Hallett <[EMAIL PROTECTED]> + + * PkgVersion.pm: Stop warning about missing packages in depends line + if an other pkg in the expression is found to statisfy it. + 2003-12-15 Daniel Macks <[EMAIL PROTECTED]>
* Services.pm: Changed expand_percent to do the automatic %% => %
Hi Justin. Do I understand this change correctly? In the past, if we had
Depends: foo | bar
and foo is present but bar is not present in the database, then the package
builds OK but issues a warning about bar not being present.
After your change, there is no longer a warning, is that correct?
If that's what this change does, then I disagree with it. It's an important reminder when people are bringing things from unstable to stable, that not everything is present in stable.
On the other hand, we should probably be more flexible in what we allow
in stable and permit people to move things like that even when there
is a warning. One possible change, which I would agree with, would
be to only issue that warning message when the verbosity level is high.
(These days, the verbosity level for users is set by default to a fairly
low value; since this warning is primarily of interest to developers,
it makes sense to only issue it if the verbosity level is high.)
We could also phrase the warning in a way that makes it clear that its
ok for developers to have packages which generate this warning message.
-- Dave
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
PGP.sig
Description: This is a digitally signed message part
