public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Edward Duffy <eduffy@cs.clemson.edu>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] common ebuild mistakes
Date: 26 May 2003 14:20:18 -0400	[thread overview]
Message-ID: <1053973218.8263.28.camel@vader> (raw)
In-Reply-To: <20030526181230.GA6277%chutz@gg3.net>

d'oh! I feel stupid.  So it's about 20-25% of the ebuild that use that
depend on it...still seems kind of low.

On Mon, 2003-05-26 at 14:12, Georgi Georgiev wrote:
> On 26/05/2003 at 13:18:44(-0400), Edward Duffy used 0.8Kbytes just to say:
> > On the one ebuild I've sumbitted, the dev that committed it added a line
> > for
> > DEPEND="virtual/glibc"
> > 
> > What wouldn't depend on glibc, isn't that a given?  A quick scan
> > through the portage directory turns up:
> > # find /usr/portage/ -iname '*.ebuild' | xargs grep "virtual/glibc" 
> >    | wc -l
> >    1982
> > # find /usr/portage/ -iname '*.ebuild' | xargs grep -v "virtual/glibc" 
> >    | wc -l
> > 406821
> 
> This gives you the number of LINES that do not have virtual/glibc, not the
> files that don't. You'd want something like:
> 
> # find /usr/portage -iname '*.ebuild' | xargs -i sh -c 'grep -q "virtual/glibc" {} || echo {}'
> 
> However, since you already have the number of packages that DO have the line -
> you only need to substract it from the total number of ebuilds.
> 
> # find /usr/portage -iname '*.ebuild' | wc -l
>    8587


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-05-26 18:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-23  1:30 [gentoo-dev] common ebuild mistakes Alastair Tse
2003-05-23  6:57 ` Dylan Carlson
2003-05-23 11:13   ` Georgi Georgiev
2003-05-23 11:39     ` Sven Vermeulen
2003-05-23  8:06 ` Paul de Vrieze
2003-05-23 12:01   ` Dhruba Bandopadhyay
2003-05-23 11:52     ` Henti Smith
2003-05-23 12:15       ` Georgi Georgiev
2003-05-23 12:11         ` Henti Smith
2003-05-23 14:43         ` Jon Portnoy
2003-05-23 14:41       ` Jon Portnoy
2003-05-23 12:08     ` Patrick Kursawe
2003-05-23 12:12       ` Dhruba Bandopadhyay
2003-05-23 12:51         ` Paul de Vrieze
2003-05-23 12:23     ` Alastair Tse
2003-05-23 19:15   ` Martin, Stephen
2003-05-23 19:39     ` Paul de Vrieze
2003-05-25 20:22     ` Aron Griffis
2003-05-28 18:43       ` Martin, Stephen
2003-05-28 20:17         ` [gentoo-dev] autoconf variables and USE (was: Re: [gentoo-dev] common ebuild mistakes) Stanislav Brabec
2003-05-26 17:18 ` [gentoo-dev] common ebuild mistakes Edward Duffy
2003-05-26 18:12   ` Georgi Georgiev
2003-05-26 18:20     ` Edward Duffy [this message]
2003-05-26 18:49       ` George Shapovalov
2003-05-26 19:05         ` Dylan Carlson
2003-05-26 19:24         ` Aron Griffis
2003-05-27  1:40           ` Zach Welch
2003-05-27 15:27             ` William McArthur

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1053973218.8263.28.camel@vader \
    --to=eduffy@cs.clemson.edu \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox