Mailing List Archive: Gentoo: User

Huge /var/tmp/portage and growing

Index | Next | Previous | View Threaded

kogorman at gmail

Sep 10, 2004, 9:27 AM

Post #1 of 11 (69 views)
Permalink

Huge /var/tmp/portage and growing

Mines over 300MB and I haven't been using portage that long.
This is awfully big for a 'tmp' tree, and it's keeping things forever.

Is there something I should have done to get this cleaned out?

++ kevin

--
Kevin O'Gorman, PhD

--
gentoo-user [at] gentoo mailing list

bruno.lists at gmail

Sep 10, 2004, 9:29 AM

Post #2 of 11 (68 views)
Permalink

Re: Huge /var/tmp/portage and growing [In reply to]

mindstormmaster at gmail

Sep 10, 2004, 10:01 AM

Post #3 of 11 (67 views)
Permalink

Re: Huge /var/tmp/portage and growing [In reply to]

I believe that /var/tmp/portage is where emerge/portage does its work
before installing a package. The source is untarred to this location
and compiled there, then copied to the final location afterward.

On Fri, 10 Sep 2004 13:29:42 -0300, Bruno Lustosa <bruno.lists [at] gmail> wrote:
> On Fri, 10 Sep 2004 09:27:05 -0700, Kevin O'Gorman <kogorman [at] gmail> wrote:
> > Mines over 300MB and I haven't been using portage that long.
> > This is awfully big for a 'tmp' tree, and it's keeping things forever.
> > Is there something I should have done to get this cleaned out?
>
> I think you can safely remove everything there.
> I've done this in the past, without a problem.
> Though I'm sure there should be a way for it to be automatically
> cleaned somehow.
>
>
>
> --
> gentoo-user [at] gentoo mailing list
>
>

--
gentoo-user [at] gentoo mailing list

danstemporaryaccount at yahoo

Sep 10, 2004, 10:34 AM

Post #4 of 11 (70 views)
Permalink

Re: Huge /var/tmp/portage and growing [In reply to]

On September 10, 2004 12:27 pm, Kevin O'Gorman wrote:
> Mines over 300MB and I haven't been using portage that long.
> This is awfully big for a 'tmp' tree, and it's keeping things forever.
>
> Is there something I should have done to get this cleaned out?

as others have mentioned, /var/tmp/portage is where your installing tarballs
are untarred and worked on when emerging. but after a successfull merge, the
files are deleted and all that should remain is a (near empty) directory tree
with a bunch of zero-byte files in them. if you have some actual files in
there (or more likely lots of files under one or two directories
under /var/tmp/portage/xyz, those are likely failed or partially merged
attempts.

deleting the whole thing is fine, portage will just recreate what it needs
next time you install something, but you might want to take a look at what
merges never finished first.

--
Everybody dies, Tracey. Somebody's carrying a bullet for you right now and
doesn't even know it. The trick is to die of old age before it finds you.
- Mal to Tracey, Firefly, "The Message"

--
gentoo-user [at] gentoo mailing list

jefklak at gmail

Sep 10, 2004, 11:15 AM

Post #5 of 11 (70 views)
Permalink

Re: Huge /var/tmp/portage and growing [In reply to]

The emerged source code normally gets deleted but if you manage to
shut down the emerge process or it's not correctly compiled, a lot of
trash stays in there, among with /var/tmp/portage/work/[current
process].

It's safe to delete it - I managed to safe about 3Gig space =)

On Fri, 10 Sep 2004 13:34:32 -0400, daniel
<danstemporaryaccount [at] yahoo> wrote:
> On September 10, 2004 12:27 pm, Kevin O'Gorman wrote:
> > Mines over 300MB and I haven't been using portage that long.
> > This is awfully big for a 'tmp' tree, and it's keeping things forever.
> >
> > Is there something I should have done to get this cleaned out?
>
> as others have mentioned, /var/tmp/portage is where your installing tarballs
> are untarred and worked on when emerging. but after a successfull merge, the
> files are deleted and all that should remain is a (near empty) directory tree
> with a bunch of zero-byte files in them. if you have some actual files in
> there (or more likely lots of files under one or two directories
> under /var/tmp/portage/xyz, those are likely failed or partially merged
> attempts.
>
> deleting the whole thing is fine, portage will just recreate what it needs
> next time you install something, but you might want to take a look at what
> merges never finished first.
>
> --
> Everybody dies, Tracey. Somebody's carrying a bullet for you right now and
> doesn't even know it. The trick is to die of old age before it finds you.
> - Mal to Tracey, Firefly, "The Message"
>
>
>
>
> --
> gentoo-user [at] gentoo mailing list
>
>

--
==============
>> Jefklak
Gentoo Linux 2.6.8.1-klak3
==============

--
gentoo-user [at] gentoo mailing list

crichey at gmail

Sep 10, 2004, 3:06 PM

Post #6 of 11 (69 views)
Permalink

Re: Huge /var/tmp/portage and growing [In reply to]

On Fri, 10 Sep 2004 09:27:05 -0700, Kevin O'Gorman <kogorman [at] gmail> wrote:
> Mines over 300MB and I haven't been using portage that long.
> This is awfully big for a 'tmp' tree, and it's keeping things forever.
>
> Is there something I should have done to get this cleaned out?
>

Any time you feel like it, except when an emerge is running:

cd /var/tmp/portage
rm -r *

I don't know why portage doesn't clean this crap.

Be aware that /usr/portage/distfiles also grows continually. I also
clean this out regularly. This means, of course, that some files must
be downloaded again if they are needed. You can search in the archives
and/or forums for some procedures that attempt to do a more
intelligent job of cleaning distfiles.

--
/\/\
(CR) Collins Richey
\/\/ "I hear you're single again." "Spouse 2.0 had fewer bugs than
Spouse 1.0, but the maintenance ... was too much for my OS."
- Glitch (tm)

--
gentoo-user [at] gentoo mailing list

rudmer at legolas

Sep 11, 2004, 12:00 AM

Post #7 of 11 (68 views)
Permalink

Re: Huge /var/tmp/portage and growing [In reply to]

On Saturday 11 September 2004 00:06, Collins Richey wrote:
> On Fri, 10 Sep 2004 09:27:05 -0700, Kevin O'Gorman <kogorman [at] gmail>
wrote:
> > Mines over 300MB and I haven't been using portage that long.
> > This is awfully big for a 'tmp' tree, and it's keeping things forever.
> >
> > Is there something I should have done to get this cleaned out?
>
> Any time you feel like it, except when an emerge is running:
>
> cd /var/tmp/portage
> rm -r *
>
> I don't know why portage doesn't clean this crap.

well, if you read this in /etc/make.conf in the FEATURES section:

# 'keeptemp' prevents the clean phase from deleting the temp files ($T)
# from a merge.
# 'keepwork' prevents the clean phase from deleting the WORKDIR.
# 'noclean' prevents portage from removing the source and temporary files
# after a merge -- for debugging purposes only.

then you would expect that portage will clean it, but it doesn't...
maybe adding 'clean' to FEATURES works?

> Be aware that /usr/portage/distfiles also grows continually. I also
> clean this out regularly. This means, of course, that some files must
> be downloaded again if they are needed. You can search in the archives
> and/or forums for some procedures that attempt to do a more
> intelligent job of cleaning distfiles.

for example this one:
http://www.leak.com.ar/~juam/code/distcleaner/

Rudmer

--
gentoo-user [at] gentoo mailing list

error at fuckinginternet

Sep 11, 2004, 1:26 AM

Post #8 of 11 (68 views)
Permalink

Re: Huge /var/tmp/portage and growing [In reply to]

Rudmer van Dijk wrote:

>On Saturday 11 September 2004 00:06, Collins Richey wrote:
>
>
>>On Fri, 10 Sep 2004 09:27:05 -0700, Kevin O'Gorman <kogorman [at] gmail>
>>
>>
>wrote:
>
>
>>>Mines over 300MB and I haven't been using portage that long.
>>>This is awfully big for a 'tmp' tree, and it's keeping things forever.
>>>
>>>Is there something I should have done to get this cleaned out?
>>>
>>>
>>Any time you feel like it, except when an emerge is running:
>>
>>cd /var/tmp/portage
>>rm -r *
>>
>>I don't know why portage doesn't clean this crap.
>>
>>
>
>well, if you read this in /etc/make.conf in the FEATURES section:
>
># 'keeptemp' prevents the clean phase from deleting the temp files ($T)
># from a merge.
># 'keepwork' prevents the clean phase from deleting the WORKDIR.
># 'noclean' prevents portage from removing the source and temporary files
># after a merge -- for debugging purposes only.
>
>then you would expect that portage will clean it, but it doesn't...
>maybe adding 'clean' to FEATURES works?
>
>
>
>>Be aware that /usr/portage/distfiles also grows continually. I also
>>clean this out regularly. This means, of course, that some files must
>>be downloaded again if they are needed. You can search in the archives
>>and/or forums for some procedures that attempt to do a more
>>intelligent job of cleaning distfiles.
>>
>>
>
>for example this one:
>http://www.leak.com.ar/~juam/code/distcleaner/
>
> Rudmer
>
>--
>gentoo-user [at] gentoo mailing list
>
>
>
>
>
>
man make.conf

FEATURES as it seems has no "clean" keyword,
but whenever I think about it I just go rm -rf * everything
in /usr/portage/distfiles and /var/tmp/portage
I can redownload those files and decompress them
again if I need to.

To each h(is|er) own, I guess. The open source way :)

--
gentoo-user [at] gentoo mailing list

thorsten at thorstenkampe

Sep 11, 2004, 7:18 AM

Post #9 of 11 (67 views)
Permalink

Re: Huge /var/tmp/portage and growing [In reply to]

* Rudmer van Dijk (2004-09-11 09:00 +0200)
> On Saturday 11 September 2004 00:06, Collins Richey wrote:
>> On Fri, 10 Sep 2004 09:27:05 -0700, Kevin O'Gorman <kogorman [at] gmail>
> wrote:
>>> Mines over 300MB and I haven't been using portage that long.
>>> This is awfully big for a 'tmp' tree, and it's keeping things forever.
>>>
>>> Is there something I should have done to get this cleaned out?
>>
>> Any time you feel like it, except when an emerge is running:
>>
>> cd /var/tmp/portage
>> rm -r *
>>
>> I don't know why portage doesn't clean this crap.
>
> well, if you read this in /etc/make.conf in the FEATURES section:
>
> # 'keeptemp' prevents the clean phase from deleting the temp files ($T)
> # from a merge.
> # 'keepwork' prevents the clean phase from deleting the WORKDIR.
> # 'noclean' prevents portage from removing the source and temporary files
> # after a merge -- for debugging purposes only.
>
> then you would expect that portage will clean it, but it doesn't...

Yes. And it should be the default that's why they're called "temporary
files".

T.

--
gentoo-user [at] gentoo mailing list

motub at planet

Sep 11, 2004, 5:02 PM

Post #10 of 11 (73 views)
Permalink

Re: Huge /var/tmp/portage and growing [In reply to]

kage wrote:
> Rudmer van Dijk wrote:
>
>> On Saturday 11 September 2004 00:06, Collins Richey wrote:
>>
>>
>>> On Fri, 10 Sep 2004 09:27:05 -0700, Kevin O'Gorman
>>> <kogorman [at] gmail>
>>
>> wrote:
>>
>>
>>>> Mines over 300MB and I haven't been using portage that long.
>>>> This is awfully big for a 'tmp' tree, and it's keeping things forever.
>>>>
>>>> Is there something I should have done to get this cleaned out?
>>>>
>>>
>>> Any time you feel like it, except when an emerge is running:
>>>
>>> cd /var/tmp/portage
>>> rm -r *
>>>
>>> I don't know why portage doesn't clean this crap.
>>>
>>
>>
>> well, if you read this in /etc/make.conf in the FEATURES section:
>>
>> # 'keeptemp' prevents the clean phase from deleting the temp files
>> ($T)
>> # from a merge.
>> # 'keepwork' prevents the clean phase from deleting the WORKDIR.
>> # 'noclean' prevents portage from removing the source and
>> temporary files
>> # after a merge -- for debugging purposes only.
>>
>> then you would expect that portage will clean it, but it doesn't...
>> maybe adding 'clean' to FEATURES works?
>>
>>
>>
>>> Be aware that /usr/portage/distfiles also grows continually. I also
>>> clean this out regularly. This means, of course, that some files must
>>> be downloaded again if they are needed. You can search in the archives
>>> and/or forums for some procedures that attempt to do a more
>>> intelligent job of cleaning distfiles.
>>>
>>
>>
>> for example this one:
>> http://www.leak.com.ar/~juam/code/distcleaner/
>>
>> Rudmer
>>
>> --
>> gentoo-user [at] gentoo mailing list
>>
>>
>>
>>
>>
>>
> man make.conf
>
> FEATURES as it seems has no "clean" keyword,

Maybe not, but /etc/make.conf does:

AUTOCLEAN="yes"

My /var/tmp/portage is 3.9 MB.

Holly

> but whenever I think about it I just go rm -rf * everything
> in /usr/portage/distfiles and /var/tmp/portage
> I can redownload those files and decompress them
> again if I need to.
>
> To each h(is|er) own, I guess. The open source way :)
>
> --
> gentoo-user [at] gentoo mailing list
>
>

--
gentoo-user [at] gentoo mailing list

ml-en at veller

Sep 12, 2004, 11:09 AM

Post #11 of 11 (68 views)
Permalink

Re: Huge /var/tmp/portage and growing [In reply to]

* Holly Bostick <motub [at] planet>:
> Maybe not, but /etc/make.conf does:
>
> AUTOCLEAN="yes"
>
> My /var/tmp/portage is 3.9 MB.

AUTOCLEAN removes outdated packages, e.g. after an update (see
/etc/make.conf.example and emerge --help). It is not there to clean your
TEMPDIR.

BTW: Please trim your answers. Thx.
--
.: Torsten Veller | Biology is the only science in which multiplication :.
.: | means the same thing as division. :.

--
gentoo-user [at] gentoo mailing list

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads