-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ciaran McCreesh wrote: > On Mon, 01 Aug 2005 19:23:37 -0400 Alec Warner <[EMAIL PROTECTED]> > wrote: > | > Hrmmmmm. Is this going to be sanely doable by your average dev? How > | > long a dep string would we be having in typical cases? How about in > | > bad cases? > | > > | The more formal the depstring, the quicker the packages build ( > | using > | only needed packages instead of lumping them in one group ). This is > | essentially what the DEPEND should be, just what the packages needs to > | compile and run. This especially benefits embedded targets who need a > | bare-bones set of libraries and nothing else. > > The problem is... By hard-coding a bunch of xorg packages, you're making > your DEPEND *less* accurate. Most packages will build just fine with > other X implementations. [1] Yes but at present we have only 1 provider of X11 in the tree (xorg). If we were to make a bunch of virtuals (concepts if you will), then all packages should/will work fine with xorg, because they are all tested with xorg. Then all of a sudden a new X server comes out, call it Foo. So we add Foo to our virtual/concept and things break...because no one has tested every package with Foo, it's only been tested with xorg.
> > Providing a specific metapackage is a bad idea. What if a package really > does depend upon xorg? Providing a specific concept would be better. > Whether such a thing is implementable currently is up for debate... > [2] Virtuals are basically concepts, things are only added to virtual/mta fex, when they fulfill the concept and real-world requirements of mta. As long as one can define exactly what the real-world requirements of each x11 concept is, then it shouldn't be a problem. Mostly this is a discussion with x11 geeks about the standard. To sum up the two pieces of the above. In order to prevent [1] we need to come up with an agreement on what constitutes each concept/virtual [2]. Virtual/x11 was originally for xfree/xorg migration, but I don't believe that there is any kind of agreed upon requirement set for a package to be added to virtual/x11. A quick grep of the tree shows 2115 ebuilds DEPEND on x11, which is a lot of ebuilds to do QA on for any new x11 provider. Most other virtuals adhere to a simple binary interface ( call sendmail, mail is sent), as opposed to X11's library based interface (although it has binaries as well.) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iQIVAwUBQu7I5mzglR5RwbyYAQLJdg/+OQf8MY16CMkmR4mceDPH+uTO+4dMwiqt MUVuXm520bH5jD0dITogxrPWNMZXLPY2topENKoCsvM0ex1hqB3/mNs9WcXre27a 4QtowNX4rFG2oBSxFUEphvJD+dH9XUptBUaecL+g286G9rqlc6DNvl7LfHTokCa6 TmG2sbArEofOQpQOa4YPDfahUp9Bzvmusb9gLKHtMPIGokbmD4fSLhNVlAsqjH9L mrs6a+ZNt1GzOVAuDnnDUYYgIhHk5J4EEPTnqfZ4ByaKokUCSSMzzJ+fJDTkNBe9 Zz++vAcR2QaER0jvL3r99r4xMM/MYzrQMG+tbZ3i8UY/RQZ5u886s4K899bcAA0s qa0W9xP61vtxghQy60tkmdvFi3y+GVRGrNwVlPi82Mi8nrCBN19sj9N6k2xVetnr esJmZ7mL+JA0gmXAfGTZ8DUpi8huPwYtKcDBRTq7F9fpPGchiy/IXTnizcv5bQF8 C0ADKSdNshKasr/iGWfP+pGgCMWDsEOqe9hR8phRoECx6N0xCRPgfP/chvKIumvs oqVW2EEB0Wk6f3vUmp/vE5qIFX1T3UQGNkHtdRnwn48Btj/C0FfuEdmGqyCbR+Yp u/jW4AZGL8MrbkpbUIzJyR7gAYe3MAYt3QcBFgRuEX2W2bhD+K7R2jy3rfzEkLx4 dcXCpCyuqSM= =7TLN -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list
