[gentoo-user] Can I delete /var/tmp/portage ?
Chris Barker
My / partition has all filled up, and that's because almost 2G is taken
up by /var/tmp/portage.
Given that it's in /var/tmp, it looks like I don't need to keep it
around, but I'm curious if that's the case, why doesn't emerge delete
stuff when it's done with it?
I might be able to move it to another partition, but I'm curious what
the downside is of just purging it.
-thanks, Chris
--
Christopher Barker, Ph.D.
Oceanographer
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
--
gento...@gentoo.org mailing list
Andrew Gaffney
> Hi all,
>
> My / partition has all filled up, and that's because almost 2G is taken
> up by /var/tmp/portage.
>
> Given that it's in /var/tmp, it looks like I don't need to keep it
> around, but I'm curious if that's the case, why doesn't emerge delete
> stuff when it's done with it?
>
> I might be able to move it to another partition, but I'm curious what
> the downside is of just purging it.
You can safely clean it out with 'rm -rf /var/tmp/portage/*'. Most of the stuff in there
is source code left over from failed compiles.
--
Andrew Gaffney
Network Administrator
Skyline Aeronautics, LLC.
636-357-1548
--
gento...@gentoo.org mailing list
Chris Barker
> You can safely clean it out with 'rm -rf /var/tmp/portage/*'. Most of
> the stuff in there is source code left over from failed compiles.
thanks. But I'm still curious, I haven't had that many failed compiles!
It seems to contain everything I've emerged. Is there a flag that will
tell emerge to clean up after itself?
-Chris
Andrew Gaffney
> Andrew Gaffney wrote:
>
>> You can safely clean it out with 'rm -rf /var/tmp/portage/*'. Most of
>> the stuff in there is source code left over from failed compiles.
>
> thanks. But I'm still curious, I haven't had that many failed compiles!
> It seems to contain everything I've emerged. Is there a flag that will
> tell emerge to clean up after itself?
Check to see if 'AUTOCLEAN="yes"' is in your /etc/make.conf. I know that it's in mine, but
I created mine a year and a half ago, so I can't remember if it was there to begin with.
Every compile will leave a few files in /var/tmp/portage, but it is usually only a few K.
Andy Herrman
on by default. :)
Glad I read your post...I hadn't realized that was there.
-Andy
Andrew Gaffney wrote:
> Chris Barker wrote:
>
>> Andrew Gaffney wrote:
>>
>>> You can safely clean it out with 'rm -rf /var/tmp/portage/*'. Most
>>> of the stuff in there is source code left over from failed compiles.
>>
>>
>> thanks. But I'm still curious, I haven't had that many failed
>> compiles! It seems to contain everything I've emerged. Is there a
>> flag that will tell emerge to clean up after itself?
>
>
> Check to see if 'AUTOCLEAN="yes"' is in your /etc/make.conf. I know
> that it's in mine, but I created mine a year and a half ago, so I
> can't remember if it was there to begin with.
>
> Every compile will leave a few files in /var/tmp/portage, but it is
> usually only a few K.
>
--
gento...@gentoo.org mailing list
Brett I. Holcomb
Check /etc/make.conf under the Features section.
> Andrew Gaffney wrote:
>
> > You can safely clean it out with 'rm -rf /var/tmp/portage/*'. Most of
> > the stuff in there is source code left over from failed compiles.
>
> thanks. But I'm still curious, I haven't had that many failed compiles!
> It seems to contain everything I've emerged. Is there a flag that will
> tell emerge to clean up after itself?
>
--
Brett I. Holcomb
--
gento...@gentoo.org mailing list
Thomas Buntrock
> Every compile will leave a few files in /var/tmp/portage, but it is usually
> only a few K.
Yes, it does. Between 8K and 100K per pkg, but with over 300 pkgs installed
mine is already up to 23M. Not that it matters ;-)
Thomas
--
gento...@gentoo.org mailing list
Chris Barker
> On Wed, 5 May 2004, Chris Barker wrote:
> Check /etc/make.conf under the Features section.
Looking there, I see a "noclean" flag, but no "clean" flag, and I have
no Features in make.conf, and in make.globals, it is:
FEATURES="sandbox ccache autoaddcvs"
However, after deleting /var/tmp/portage, I then try to
emerge openoffice
and end up with a 1.9GB portage dir, and a full partition, and a failed
build. I know openoffice is big, but is it really that big?
Any other ideas?
Keith Gosse
my partition with about 2 gigs and then crashes. Any solutions /
suggestions?
On May 6, 2004, at 10:33 AM, Chris Barker wrote:
>
>
> and end up with a 1.9GB portage dir, and a full partition, and a
> failed build. I know openoffice is big, but is it really that big?
>
> Any other ideas?
_____________________________________________________
Keith Gosse, Resource Room Teacher, School Counselor Thornhill Jr.
Secondary School, Terrace, B.C., V8G 4N8
--
gento...@gentoo.org mailing list
Ernie Schroder
OO needs massive ammounts of disk space to compile. I would suggest that you
install openoffice-bin. I see no difference in performance over built from
source and a 3 to 5 second difference in time to open the app. If you think
that you will start open office 6,000 times or more before the next time you
update it, then by all means, clear out some space and build from source.
--
Regards, Ernie
100% Microsoft and Intel free
--
gento...@gentoo.org mailing list
Robert Crawford
I recall reading in the gentoo forum, or somewhere, that Open Office takes up
to 5GB free working space to compile in, and if that's true, when your
partition gets filled up with work files while OO is compiling, it crashes.
It's simply running out of space to work in.
There are compiled binaries you can emerge, but of course the downside of
that is it won't be optimzed and compiled for your specific machine. I'm not
sure if they only offer one generic version (like 586), or have other
versions for different architectures.
Robert Crawford
--
gento...@gentoo.org mailing list
Chris Barker
> I recall reading in the gentoo forum, or somewhere, that Open Office takes up
> to 5GB free working space to compile in,
well, that explains it! I'm emerging the binary version now. I hardly
ever use it anyway.
thanks, all.
Neil Bothwick
> I see no difference in performance over built from
> source and a 3 to 5 second difference in time to open the app. If you
> think that you will start open office 6,000 times or more before the
> next time you update it, then by all means, clear out some space and
> build from source.
That's not a realistic comparison. You spend that 3-5 seconds looking at
the OOo splash graphic, wishing the damn thing would hurry up. Compiling
takes up none of your time, it happens in the background or while
you're asleep.
--
Neil Bothwick
NOTICE:
-- THE ELEVATORS WILL BE OUT OF ORDER TODAY --
(The nearest working elevators are in the building
across the street.)
Daevid Vincent
Then I did an emerge update and I still have stuff in /var/tmp/portage/ ??
--
gento...@gentoo.org mailing list
Simon Roby
could be a problem for some people (personally I compile openoffice only so I
can get it in French).
On May 6, 2004 1442, Ernie Schroder wrote:
> OO needs massive ammounts of disk space to compile. I would suggest that
> you install openoffice-bin. I see no difference in performance over built
> from source and a 3 to 5 second difference in time to open the app. If you
> think that you will start open office 6,000 times or more before the next
> time you update it, then by all means, clear out some space and build from
> source.
--
gento...@gentoo.org mailing list
Simon Roby
> I have the AUTOCLEAN="yes" in my /etc/make.conf
>
> Then I did an emerge update and I still have stuff in /var/tmp/portage/ ??
>
How big is that leftover stuff? It's normal for Portage to leave a few Ks
after an emerge, even if AUTOCLEAN is enabled.
--
gento...@gentoo.org mailing list
Daevid Vincent
Doesn't sound very "clean" to me then... :(
> -----Original Message-----
> From: Simon Roby [mailto:sham...@hotmail.com]
> Sent: Thursday, May 06, 2004 6:09 PM
> To: gento...@lists.gentoo.org
> Subject: Re: [gentoo-user] Can I delete /var/tmp/portage ?
>
--
gento...@gentoo.org mailing list
Neil Bothwick
> I have the AUTOCLEAN="yes" in my /etc/make.conf
>
> Then I did an emerge update and I still have stuff in
> /var/tmp/portage/ ??
AUTOCLEAN is nothing to do with /var/tmp/portage/ (or wherever
$PORTAGE_TMPDIR points). according to make.conf
# AUTOCLEAN enables portage to automatically clean out older or overlapping
# packages from the system after every successful merge. This is the
# same as running 'emerge -c' after every merge. Set with: "yes" or "no".
#AUTOCLEAN="yes"
--
Neil Bothwick
A printer consists of three main parts: the case, the jammed paper tray
and the blinking red light.
Andrew Gaffney
> On Thu, 6 May 2004 16:20:31 -0700, Daevid Vincent wrote:
>
>
>>I have the AUTOCLEAN="yes" in my /etc/make.conf
>>
>>Then I did an emerge update and I still have stuff in
>>/var/tmp/portage/ ??
>
>
> AUTOCLEAN is nothing to do with /var/tmp/portage/ (or wherever
> $PORTAGE_TMPDIR points). according to make.conf
>
> # AUTOCLEAN enables portage to automatically clean out older or overlapping
> # packages from the system after every successful merge. This is the
> # same as running 'emerge -c' after every merge. Set with: "yes" or "no".
> #AUTOCLEAN="yes"
I guess that's what I get for posting before thinking. Like I said, it has been
quite a while since I originally created my /etc/make.conf.
Keith Gosse
- (gotta compile!!)
I moved my /usr (which was about 6 gig with portage in it) from my /
partition to a separate /usr partition (now both are 9 gig). Now I
have lots of room in /var/tmp for the big compiles.
Thanks to those with the wisdom to point me in the right direction.
Keith
_____________________________________________________
Keith Gosse, Resource Room Teacher, School Counselor Thornhill Jr.
Secondary School, Terrace, B.C., V8G 4N8
--
gento...@gentoo.org mailing list
Norberto Bensa
> I moved my /usr (which was about 6 gig with portage in it) from my /
> partition to a separate /usr partition (now both are 9 gig). Now I
> have lots of room in /var/tmp for the big compiles.
Just get a big partition (for OOo more than 3GB) and then:
PORTAGE_TMPDIR=/path/to/your/big/partition emerge openoffice
--
gento...@gentoo.org mailing list
Robert Crawford
> Some might be interested in how I solved the OpenOffice compile problem
> - (gotta compile!!)
>
> I moved my /usr (which was about 6 gig with portage in it) from my /
> partition to a separate /usr partition (now both are 9 gig). Now I
> have lots of room in /var/tmp for the big compiles.
>
> Thanks to those with the wisdom to point me in the right direction.
>
> Keith
Keith,
Good solution. Let us know how the OO compile goes. One question: How come you
didn't just move /var to it's own partition instead of /usr? Was there a
specific reason you wanted /usr on it's own partition? I guess it doesn't
really matter which way it's done, as long as /var/tmp/portage ends up with
enough space for the OO compile to work in.
Keith Gosse
partitions. To move /var would still leave my root partition quite
full.
This way I got lots of room for /var to flex its muscles during a
compile. Compile is not finished yet but is looking good. It's quite
interesting to watch the partition fill as the software is compiled -
never paid any attention before. :-)
Keith
Chris Barker
> Each dir is a different. Ranging from 4k to 108k with 5 dirs.
>
> Doesn't sound very "clean" to me then... :(
AUTOCLEAN means something different anyway:
man make.conf:
AUTOCLEAN = ["yes" | "no"]
Automatically cleans the system by removing outdated
packages
which will not remove functionalities or prevent your
system
from working.
It's not about removing source, etc from the portage tree
What you want to make sure is that:
[keeptemp, keepwork, noclean] are not in your make.global or make.conf
However, it seems that somethings going to get left behind anyway, but I
know I was only concerned about GB, not KB
-Chris
Neil Bothwick
> I just moved the directory that would give me the most balanced set of
> partitions. To move /var would still leave my root partition quite
> full.
You didn't need to move anything, just change the value of
PORTAGE_TMPDIR in make.conf.
--
Neil Bothwick
If we aren't supposed to eat animals, why are they made of meat?
Keith Gosse
constructs of the distribution.
Unfortunately, I don't have it all under my belt yet, thanks for the
advice (to be used next time).
Keith
> You didn't need to move anything, just change the value of
> PORTAGE_TMPDIR in make.conf.
>
>
> --
> Neil Bothwick
>
> If we aren't supposed to eat animals, why are they made of meat?
>
Robert Crawford
> I just moved the directory that would give me the most balanced set of
> partitions. To move /var would still leave my root partition quite
> full.
> This way I got lots of room for /var to flex its muscles during a
> compile. Compile is not finished yet but is looking good. It's quite
> interesting to watch the partition fill as the software is compiled -
> never paid any attention before. :-)
>
> Keith
That makes perfect sense, but now that I think about it, I like Norberto
Bensa's suggestion a little better:
"Just get a big partition (for OOo more than 3GB) and then:
PORTAGE_TMPDIR=/path/to/your/big/partition emerge openoffice"
Assuming you had enough free space, or a bigger partition, say "/data," or
whatever, you could just temporarily point PORTAGE_TMPDIR= there, and
compile OO, then change it back to /var/tmp. Of course in your case, you
wanted to free up some / space.
Keith Gosse
, I did not get a clean compile first attempt after moving /usr - I
did discover that after solving the "hard drive full" issue that a
second issue became apparent: - distcc sharing the compile with my
other machine was killing the build as well! I removed distcc from my
make.conf and the build was successful (although a lot slower) :-)
/tmp usage was about 5 gig for the compile, just as the more
knowledgeable compilers knew.
Regards,
Keith
Daevid Vincent
I have 915 .tar.gz files taking up 1.8GB of precious space on my notebook
that only allocates 10GB for Gentoo.
--
gento...@gentoo.org mailing list
Collins Richey
Rumen Yotov <rumen...@dir.bg> wrote:
I'm just curious. Does anyone have any statistics. My guess is that less
than 2% of these files are ever referenced again.
Oh, and you can remove the contents of /var/tmp/portage as well.
--
/\/\
( CR ) Collins Richey
\/\/
--
gento...@gentoo.org mailing list
Bill Kenworthy
1. system rebuild: needs every file
2. new system: copy all files over (or nfs mount distfiles, or ...) -
needs every file
3. change use flags (some with wide application, or CFLAGS (optimisation
or cpu choices), needs every file (system rebuild)
4. -rn revisions and updates - needs specific files
1-3 is something that is especially important to modem or restricted
connection users - broadband can probably ignore it and download on
demand.
There are utilities that trawl through and just keep installed versions
if keeping everything is worring you.
Basicly if you have the space, it will save a lot of time in even
general maintenance updates.
BillK
On Wed, 2004-06-30 at 10:14, Collins Richey wrote:
> On Wed, 30 Jun 2004 05:09:33 +0300
> Rumen Yotov <rumen...@dir.bg> wrote:
>
> I'm just curious. Does anyone have any statistics. My guess is that less
> than 2% of these files are ever referenced again.
--
gento...@gentoo.org mailing list
Iain Buchanan
> Can I delete all the stuff in /usr/portage/distfiles ??
> I have 915 .tar.gz files taking up 1.8GB of precious space on my notebook
> that only allocates 10GB for Gentoo.
Try this attachment first (it came from the list) it's not quite so
brutal. It just deletes packages that seem to have newer versions
also. But beware! It will delete linux-2.4.x in favour of linux-2.6.x,
and X11R6.7.0-src[1-7] in favour of X11R6.7.0-src7.
--
Iain Buchanan <iai...@netspace.net.au>
Norberto Bensa
> Try this attachment first (it came from the list) it's not quite so
Bah. Who needs Perl?
This came from gentoo-dev a year ago:
Alec Berryman wrote:
> bash <(comm -23 <(find /usr/portage/distfiles/ -maxdepth 1 -type f -printf
> %f\\n | sort) <(find /usr/portage/ /usr/local/portage/ -path
> '*/*/files/digest-*' -print0 | xargs -0 awk '{print $3}' | sort -u) | sed
> -e 's|^|rm -i /usr/portage/distfiles/|')
Nice one, really.
Regards,
Norberto
--
gento...@gentoo.org mailing list
Jeff Smelser
Hash: SHA1
On Tuesday 29 June 2004 09:14 pm, Collins Richey wrote:
> I'm just curious. Does anyone have any statistics. My guess is that less
> than 2% of these files are ever referenced again.
That actually seems high to me. Unless your networking distfiles.
Jeff
- --
=======================================================================
Jabber: tradergt@(smelser.org|jabber.org)
Quote: A feature is a bug with seniority.
=======================================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFA4kFQld4MRA3gEwYRAkb4AKCxAfl9RMVhU0lixb70gABB/oSqAwCgtv0q
ceTtJczO2tzj/QZMPhqiZkw=
=523S
-----END PGP SIGNATURE-----
--
gento...@gentoo.org mailing list
Neil Bothwick
> Your not looking at it from the right angle
> 1. system rebuild: needs every file
> 2. new system: copy all files over (or nfs mount distfiles, or ...) -
> needs every file
> 3. change use flags (some with wide application, or CFLAGS
> (optimisation or cpu choices), needs every file (system rebuild)
Delete the old versions and backup the rest to CD. That way you free up
the space yet still have the files should you need them.
--
Neil Bothwick
I'm writing a book. I've got the page numbers done.
Neil Bothwick
> I'm just curious. Does anyone have any statistics. My guess is that
> less than 2% of these files are ever referenced again.
It depends on what you do. For example, there have been seven versions
of gentoo-dev-sources released so far, each one using the same kernel
tarball. kdenetwork was recently updated, to fix Yahoo's IM changes.
Once again, the change was a patch, using the same main tarball.
Almost every time you install a -r<n> ebuild, you are re-using the
previous tarball. It probably affect ~arch users more, especially those
that sync every day.
--
Neil Bothwick
All wight - Rho sritched mg kegtops awound?
Adrian CAPDEFIER
"Drop them like un ugly baby"
almost 20% of your space wasted by compiled source files which you can
always download ... bah
Adi.
--
gento...@gentoo.org mailing list
Eugene Rosenzweig
the next update comes along. Much better solution is a script floating
around the forums which will clean the /usr/portage/distfiles of the old
versions of packages that are no longer used by the system. Here, I found
some info: http://forums.gentoo.org/viewtopic.php?t=67849
Eugene.
> -----Original Message-----
> From: Adrian CAPDEFIER [mailto:adrianc...@digifin.ro]
> Sent: Wednesday, 30 June 2004 9:04 PM
> To: gento...@lists.gentoo.org
--
gento...@gentoo.org mailing list
Gearoid Donnellan
useless internet connection so I have to keep the distfiles just
incase anything goes wrong. If you have the bandwidth you should
delete them
--
gento...@gentoo.org mailing list
Neil Bothwick
> It depends on your situation. At the moment I have an incredibly
> useless internet connection so I have to keep the distfiles just
> incase anything goes wrong. If you have the bandwidth you should
> delete them
Show me a network that has more bandwidth than ATA.
Unless you are strapped for disk space, you may as well hang onto them.
delete the outdated package by all means, but the current packages are
best left in there.
Do you really want to download 35MB of kernel sources (or 211MB of OOo)
over again just to apply a small security patch?
--
Neil Bothwick
Please Captain, not in front of the Klingons. * Spock
Gearoid Donnellan
> noname - 1K
>
--
gento...@gentoo.org mailing list
Collins Richey
"Eugene Rosenzweig" <euge...@dodo.com.au> wrote:
> Deleting them means that sometimes you will need to re-download them
> when the next update comes along. Much better solution is a script
> floating around the forums which will clean the /usr/portage/distfiles
> of the old versions of packages that are no longer used by the system.
> Here, I found some info:
> http://forums.gentoo.org/viewtopic.php?t=67849
>
Here's my final comments.
1. Yes, there are a few packages (kernel, X..., and a few others) that
download a base tarball and patch up to the new version, Most of the
packages I've seen just download a new tarball - no patches.
2. The 4-5 times in 5 years that I've needed to emerge a package with a
change in USE, etc., don't amount to a hill of beans in comparison to
the packages that are replacement tarballs each time. Even if I had only
dial-up access, those few extra packages to download wouldn't make much
difference.
3. You pays you money (i.e. bandwidth) you takes you chances. If you
have lots of available disk space, keep the packages and space be
damned. If disk space is tight, just delete the packages (both
/usr/portage/distfiles and /var/tmp/portage) and worry less. That's what
I've done for years. I, of course, am on cable, so the few extra minutes
transfer each week are trivial. I used to keep the kernel sources and a
few others, but I don't even do that any more. My system amounts
typically to about 5.4G (/home is separate). When df reports 6G or more,
I just whack everything with no remorse.
YMMV,