public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Vitaly Kushneriuk <vitaly_kushneriuk@yahoo.com>
To: Gentoo-dev <gentoo-dev@gentoo.org>
Subject: Re: AW: [gentoo-dev] Sys-Cleanup after build complete
Date: 18 Feb 2002 06:05:02 +0200	[thread overview]
Message-ID: <1014005102.5930.8.camel@uranus.u235.eyep.net> (raw)
In-Reply-To: <000d01c1b926$b15184d0$be01a8c0@KISSWebMedias>

Ok. So once *-devel packages are available, you'v got the solution.
I mean the script below ;-)

On Tue, 2002-02-19 at 11:20, Sebastian Werner wrote:
> 
> Like rpm in the big distros like Mandrake. I know. ;-) But you must
> unmerge each package you won't after building complete. While building
> you need some -devel-packages. But afterwards you must delete them. I
> like this cleanup function to remove all -devel packages. Something
> like:
> 
> for i in `find /var/db/pkg -name "*-devel.ebuild"`; do
>   ebuild $i unmerge
> done
> 
> Ok this is easier and cleaner then without "-devel" packages. ;-))
> 
> 
> Greetings
> 
> Sebastian
> 
> -----Ursprüngliche Nachricht-----
> Von: gentoo-dev-admin@gentoo.org [mailto:gentoo-dev-admin@gentoo.org] Im
> Auftrag von Vitaly Kushneriuk
> Gesendet: Montag, 18. Februar 2002 04:51
> An: Gentoo-dev
> Betreff: Re: [gentoo-dev] Sys-Cleanup after build complete
> 
> Your problem can be solved with sub-packaging. i.e. producing
> more then one package from the same ebuild. like glibc and glibc-devel.
> This feature is considered for the next generation of portage (after 1.0
> is out).
> 
> 	/Vitaly
> On Tue, 2002-02-19 at 11:00, Sebastian Werner wrote:
> > Hey
> >  
> > Is it possible to integrate a function in portage which cleans up the
> > system after build is complete. On many desktop systems I like to have
> > my hdd-space for my work and not for all these include-files. I don’t
> > know which files I could delete after system is complete. I like
> > something like a DEVELOPER=”yes” flag in make.conf to enable that all
> > includes will be copied like now. And if not enabled to delete files
> > with a ‘ebuild sysclean’ which are not needed anymore.
> >  
> > Thanks in advance
> >  
> > Sebastian
> >  
> > ---
> >  
> > Sebastian Werner
> > Paritätische Sozialdienste Minden-Lübbecke
> >  
> > Anschrift:  Simeonstraße 19
> >             32423 Minden
> >  
> > Telefon:    0571.8280220
> > Homepage:   http://www.paritaet-minden-luebbecke.de
> >  
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev



  reply	other threads:[~2002-02-19  9:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000601c1b923$f0d57740$be01a8c0@KISSWebMedias>
2002-02-18  3:50 ` [gentoo-dev] Sys-Cleanup after build complete Vitaly Kushneriuk
2002-02-19  9:20   ` AW: " Sebastian Werner
2002-02-18  4:05     ` Vitaly Kushneriuk [this message]
2002-02-19 14:25   ` Dave Lee
2002-02-19 14:00     ` Bob Phan
2002-02-19 18:42       ` George Shapovalov
2002-02-19 15:00     ` Vitaly Kushneriuk

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=1014005102.5930.8.camel@uranus.u235.eyep.net \
    --to=vitaly_kushneriuk@yahoo.com \
    --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