Re: [gentoo-dev] Sys-Cleanup after build complete

Re: [gentoo-dev] Sys-Cleanup after build complete

[Vitaly Kushneriuk]

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
>  

AW: [gentoo-dev] Sys-Cleanup after build complete

[Sebastian Werner]

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

Re: AW: [gentoo-dev] Sys-Cleanup after build complete

[Vitaly Kushneriuk]

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

Re: [gentoo-dev] Sys-Cleanup after build complete

[Dave Lee]

Vitaly Kushneriuk wrote:
> 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).

Is there anybody else out there other than me who doesnt like this?
my experience is with rpm based systems and I hate the proliferation of
-devel packages and other subpackages. thats one thing I really like about 
portage is that I dont have to deal with that, I install a package and it
comes with everything.  I know there are advantages to having -devel and
other subpackages like the rpm systems use, such as finer grained control
of what is and isnt installed, but as a user and administrator I hate
having extra packages installed as though they are different from the
package itself.  most software compiled from source will install the devel
files, and I think portage should too.  maybe a solution is to have a
USE_DEVEL that is used similar to USE, and can be default set to "*" for
everything.  another possibility is to have a --option to emerge so that
emereg doesnt install devel files.  I am new to gentoo so forgive me if
these ideas suck and I will just shutup in that case. 

thanks,
Dave

Re: [gentoo-dev] Sys-Cleanup after build complete

[Bob Phan]

On Tue, 19 Feb 2002 07:25:02 -0700
Dave Lee <davel@canuck.com> wrote:

> 
> Vitaly Kushneriuk wrote:
> > 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).
> 
> Is there anybody else out there other than me who doesnt like this?
> my experience is with rpm based systems and I hate the proliferation
> of-devel packages and other subpackages. thats one thing I really like
> about portage is that I dont have to deal with that, I install a
> package and it comes with everything.  I know there are advantages to
> having -devel and other subpackages like the rpm systems use, such as
Yes, I also agree that sub-packaging is a bad idea.  But also, it would
be completely useless in a system where almost all software is compiled
from source.  If you were to remove the devel packages after building a
particular app, portage would just have to re-emerge the devel package
again every single time you wanted to build something that depended on
the library in question.  Devel packages only really apply to libraries,
and not apps, so yes, this would come up often.  Imagine having to
re-emerge glib every time you wanted to install something.  I don't
think that the few kilobytes you save from deleting a few header files
is really all that advantageous.  RPM gets away with it because they're
packages are all precompiled and only need runtime dependancies.  Let's
face it, the main reason we all use gentoo is because we really dislike
binary packages.

-- 
/*
 * Bob Phan <bob@evil-core.com,rphan@nrgn.com>
 * Computational Chemistry Informatics
 * Neurogen Corporation
 * (203)488-8201 x4645
 *
 * To understand recursion, you must first understand recursion.
 */

Re: [gentoo-dev] Sys-Cleanup after build complete

[George Shapovalov]

I want to support this point by saying, that in my experience things tend to 
break eventually, whenever you try to separate headers (as well as any other 
"devel" part) from the "functional" component of the package.
Besides gentoo does not keep sources around, therefore benefit of doing this 
subpackaging will be quite small, as was pointed out. One possibility though 
which comes to my mind is to cut on docs, which I personally somewhat 
dislike, but others may opt for. Here you might save a good deal (think 
glibc). Well, the docs are already compressed, so that negates somewhat the 
point but still, there might be some switch in /etc/make.conf provided.This 
does not require subpackaging, and seems easier to implement.

Another thing I just thought of. Ebuilds  contain two kinds of dependencies - 
build and run-time. So it seems that at least part of infrastructure is in 
place already. However was the correct placment of dependencies under 
these variables ever enforced? With many people contributiong we might have 
problems when the switch will take place. This is not to argue to/against the 
proposed topic apparently, but I think worth mentioning.

Geogre 


On Tuesday 19 February 2002 06:00, you wrote:
> On Tue, 19 Feb 2002 07:25:02 -0700
>
> Dave Lee <davel@canuck.com> wrote:
> > Vitaly Kushneriuk wrote:
> > > 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).
> >
> > Is there anybody else out there other than me who doesnt like this?
> > my experience is with rpm based systems and I hate the proliferation
> > of-devel packages and other subpackages. thats one thing I really like
> > about portage is that I dont have to deal with that, I install a
> > package and it comes with everything.  I know there are advantages to
> > having -devel and other subpackages like the rpm systems use, such as
>
> Yes, I also agree that sub-packaging is a bad idea.  But also, it would
> be completely useless in a system where almost all software is compiled
> from source.  If you were to remove the devel packages after building a
> particular app, portage would just have to re-emerge the devel package
> again every single time you wanted to build something that depended on
> the library in question.  Devel packages only really apply to libraries,
> and not apps, so yes, this would come up often.  Imagine having to
> re-emerge glib every time you wanted to install something.  I don't
> think that the few kilobytes you save from deleting a few header files
> is really all that advantageous.  RPM gets away with it because they're
> packages are all precompiled and only need runtime dependancies.  Let's
> face it, the main reason we all use gentoo is because we really dislike
> binary packages.

Re: [gentoo-dev] Sys-Cleanup after build complete

[Vitaly Kushneriuk]

On Tue, 2002-02-19 at 16:25, Dave Lee wrote:
> 
> 
> Vitaly Kushneriuk wrote:
> > 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).
> 
> Is there anybody else out there other than me who doesnt like this?
> my experience is with rpm based systems and I hate the proliferation of
> -devel packages and other subpackages. thats one thing I really like about 
> portage is that I dont have to deal with that, I install a package and it
> comes with everything.  I know there are advantages to having -devel and
> other subpackages like the rpm systems use, such as finer grained control
> of what is and isnt installed, but as a user and administrator I hate
> having extra packages installed as though they are different from the
> package itself.  most software compiled from source will install the devel
> files, and I think portage should too.  maybe a solution is to have a
> USE_DEVEL that is used similar to USE, and can be default set to "*" for
> everything.  another possibility is to have a --option to emerge so that
> emereg doesnt install devel files.  I am new to gentoo so forgive me if
> these ideas suck and I will just shutup in that case. 
There's no clear idea yet as to how the sub packaging will work.
But, in general, the Gentoo way is to provide user with the maximum
control that is practical, with reasonable defaults for those that
dont't care and want it to be simple. So in this case I guess, you'll be
able to chose if you want all that -devel stuff. Or may be not ;) We'll
see.

	/Vitaly