On Thu, 18 Aug 2005 16:19:59 -0700, Mark Knecht wrote: > Beyond Mozilla splitting out portions of it's functionality it > seems to me that, as a pure user type, I have no way of determining > what a given flag is intending to do when emerge is run. If, for > instance, there was some query through emerge that told me something > about what feature a flag was enabling then in this case (possibly) > we'd see that Unison was depending on Mozilla's mail features, or > Mozilla's browser features, or Mozilla's SDK. If it told me it was SDK > then clearly I wouldn't expect Firefox to provide that. If it's a > browser feature then I think I'd be warranted in asking why it didn't > accept Firefox.
It wouldn't help in this case, because Unison does not depend on Mozilla, nor does it use the mozilla USE flag. You can get the sort of information you need by reading the ebuild, USE flag settings normally alter configure options. Some way of getting this information in plain English would be nice, but that would require it to be added to every ebuild individually. -- Neil Bothwick Loose bits sink chips.
pgpG0OFA6LopC.pgp
Description: PGP signature
