Hi to all,

may I move the /usr/portage directory to /var/portage and replace in /usr
the portage with a symlink? Are there some weird effect in this operation?

My usr directory is too big

thanks

The Surfer

in Silver Surfer's honest opinion:

> Hi to all,
>
> may I move the /usr/portage directory to /var/portage and replace in /usr
> the portage with a symlink? Are there some weird effect in this operation?
>
> My usr directory is too big
>
> thanks
>
> The Surfer

from /etc/make.conf.example:

[...]
# PORTDIR is the location of the portage tree. This is the repository
# for all profile information as well as all ebuilds. This directory
# itself can reach 200M. WE DO NOT RECOMMEND that you change this.
#PORTDIR=/usr/portage
[...]

can someone explain why isn't it recommended? for emerge sync? or generic
emerge/ebuild operations?

PS:
by the way i think it shouldn't make any trouble using symlink
to /var/portage. also you could resize your partitions with partition
editor 'parted' (supports ext, fat, reiserfs and swap).
--
Hekaton Keires,
En to phronein maedhen aedistos bios.

in Hekaton Keires's honest opinion:

>> My usr directory is too big

> # for all profile information as well as all ebuilds. This directory
> # itself can reach 200M.

the only directories that should increase in size drastically should be

/usr/portage/distfiles
/usr/portage/pakcages

so maybe you'd rather move only that ones to /var/portage and then create
symlinks to them (in order prevent any possible problem with db)

try this

du -sh --exclude=distfiles --exclude=packages /usr/portage

to see how big is your PORTDIR without tarballs.
--
Hekaton Keires,
En to phronein maedhen aedistos bios.

Il Tue, 28 Dec 2004 12:17:04 +0100, Hekaton Keires ha scritto:

> in Hekaton Keires's honest opinion:
>
>>> My usr directory is too big
>
>> # for all profile information as well as all ebuilds. This directory
>> # itself can reach 200M.
>
> the only directories that should increase in size drastically should be
>
> /usr/portage/distfiles
> /usr/portage/pakcages
>
> so maybe you'd rather move only that ones to /var/portage and then create
> symlinks to them (in order prevent any possible problem with db)
>
> try this
>
> du -sh --exclude=distfiles --exclude=packages /usr/portage
>
> to see how big is your PORTDIR without tarballs.

Thanks I will move only distribution files and binaries pkgs !

bye

On Tue, 28 Dec 2004, Hekaton Keires <remove_this_hekatonkeires@hotmail.com> wrote:

> in Hekaton Keires's honest opinion:
>
>>> My usr directory is too big
>
>> # for all profile information as well as all ebuilds. This directory
>> # itself can reach 200M.
>
> the only directories that should increase in size drastically should be
>
> /usr/portage/distfiles
> /usr/portage/pakcages
>
> so maybe you'd rather move only that ones to /var/portage and then create
> symlinks to them (in order prevent any possible problem with db)

Move them and modify the variables in /etc/make.conf instead of setting
up a symbolic link.

This quote from my modified /etc/make.conf shows how I moved a bunch of
stuff to my /saves partition:

# Relocate some stuff off the root partition:
#
# PORTAGE_TMPDIR is the location portage will use for compilations and
# temporary storage of data. This can get VERY large depending upon
# the application being installed.
PORTAGE_TMPDIR=/saves/portage/temp
#
# DISTDIR is where all of the source code tarballs will be placed for
# emerges. The source code is maintained here unless you delete
# it. The entire repository of tarballs for gentoo is 9G. This is
# considerably more than any user will ever download. 2-3G is
# a large DISTDIR.
DISTDIR=/saves/portage/sources
#
# PKGDIR is the location of binary packages that you can have created
# with '--buildpkg' or '-b' while emerging a package. This can get
# upto several hundred megs, or even a few gigs.
PKGDIR=/saves/portage/packages
#
# PORT_LOGDIR is the location where portage will store all the logs it
# creates from each individual merge. They are stored as NNNN-$PF.log
# in the directory specified. This is disabled until you enable it by
# providing a directory. Permissions will be modified as needed IF the
# directory exists, otherwise logging will be disabled. NNNN is the
# increment at the time the log is created. Logs are thus sequential.
PORT_LOGDIR=/saves/portage/logs
#
# PORTDIR_OVERLAY is a directory where local ebuilds may be stored without
# concern that they will be deleted by rsync updates. Default is not
# defined.
PORTDIR_OVERLAY=/saves/portage/saved-ebuilds



--
Bobby Bryant
Austin, Texas