| 1 |
On the one ebuild I've sumbitted, the dev that committed it added a line |
| 2 |
for |
| 3 |
DEPEND="virtual/glibc" |
| 4 |
|
| 5 |
What wouldn't depend on glibc, isn't that a given? A quick scan |
| 6 |
through the portage directory turns up: |
| 7 |
# find /usr/portage/ -iname '*.ebuild' | xargs grep "virtual/glibc" |
| 8 |
| wc -l |
| 9 |
1982 |
| 10 |
# find /usr/portage/ -iname '*.ebuild' | xargs grep -v "virtual/glibc" |
| 11 |
| wc -l |
| 12 |
406821 |
| 13 |
|
| 14 |
So most ebuilds don't do this anyway. What's the rule of thumb for |
| 15 |
adding this as a dep? |
| 16 |
|
| 17 |
On Thu, 2003-05-22 at 21:30, Alastair Tse wrote: |
| 18 |
> Hi, |
| 19 |
> |
| 20 |
> I've written up a list of common mistakes that users make when |
| 21 |
> submitting ebuilds to us for inclusion. This stems from the discussion |
| 22 |
> earlier on the list about the quality of user-submitted ebuilds. |
| 23 |
|
| 24 |
|
| 25 |
|
| 26 |
-- |
| 27 |
gentoo-dev@g.o mailing list |
Archives