| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Fabio Erculiani wrote: |
| 5 |
| Hi Joshua, |
| 6 |
| I never had issues with my emails. So I don't really know what to |
| 7 |
| answer you regarding to your issues :) |
| 8 |
| SPLIT: Although I think it can be a suboptimal thing for us, I can |
| 9 |
| understand your policy. Let me add that, to me, the biggest issue is |
| 10 |
| about (R)DEPEND. Splitting packages and maintaining in an overlay it's |
| 11 |
| not that hard. |
| 12 |
| |
| 13 |
| |
| 14 |
| |
| 15 |
I personally have no desire to follow the redhat/debian/other binary |
| 16 |
packaging systems which split up infinitesimally small packages. It |
| 17 |
causes a lot more busywork in my opinion then any potential benefits |
| 18 |
that it gains you. |
| 19 |
|
| 20 |
As far as the depend issue you mentioned: Having both Rdepends and |
| 21 |
Depends isn't as far as I'm aware part of any EAPI currently (Correct me |
| 22 |
if I'm wrong people). Rdepends are needed for the builds so you will |
| 23 |
often see either RDEPENDS=${DEPEND} or vice versa. If its not there then |
| 24 |
its more of a matter of accounting then anything. I would think, and |
| 25 |
correct me if I'm wrong again, that it would make sense that if you only |
| 26 |
have RDEPENDS or DEPEND, then those same applications are required in |
| 27 |
the runtime of the application. Does it need to be explicitly stated? So |
| 28 |
far the three package manager that I'm aware of all manage this fine. |
| 29 |
Those being portage, paludis, and pkgcore. If there are other package |
| 30 |
managers out there that might have issues Its a perfect example of a |
| 31 |
reason to be involved in the EAPI discussions to help define what is |
| 32 |
needed and where. |
| 33 |
|
| 34 |
So what I suggest to you is perhaps looking over the EAPI=0 draft |
| 35 |
documentation and proposing some additions and or modifications that |
| 36 |
benefit everyone (not just one person), as its designed to be a standard |
| 37 |
for anyone who makes use of ebuilds and beyond. |
| 38 |
|
| 39 |
http://dev.gentoo.org/~spb/pms.pdf |
| 40 |
|
| 41 |
Is the current form, but halcy0n is working on an updated version of it |
| 42 |
for the next council meeting. |
| 43 |
-----BEGIN PGP SIGNATURE----- |
| 44 |
Version: GnuPG v2.0.7 (GNU/Linux) |
| 45 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 46 |
|
| 47 |
iD8DBQFH2bL22ZWR0Jhg/EsRAkduAJsGBKKl5HgR5YXziPn9yOLbi5F5MwCfacIC |
| 48 |
b/aqsokP3A6JFJ7hO4LGNXY= |
| 49 |
=BGqi |
| 50 |
-----END PGP SIGNATURE----- |
| 51 |
-- |
| 52 |
gentoo-dev@l.g.o mailing list |
Archives