Matthew Kennedy <[EMAIL PROTECTED]> writes: > [snip]
> This has been on of those minor complaints I have personally. > IMHO we should go with the following as a default: > /usr/portage/packages -> /var/cache/packages > /usr/portage -> /usr/share/portage I agree packages should go to /var/cache/, but perhaps in a subdirectory in /var/cache/portage, such as /var/cache/portage/packages. The portage ebuild tree also qualifies as cache data, however, since it is just a local mirror of the CVS repository (via rsync). Furthermore, as I have previously stated, it is useful to store it on /var because it changes frequently, and thus tends to fragment the filesystem on which it resides. Likewise, the distfiles directory is also cache data, and will also lead to fragmentation. As far as the argument that there is no reason to want to keep /usr mounted read-only and still update the portage tree, one reason might be that portage is useful for determining if there is something to update, and so someone might want to use portage to determine that, and then only remount /usr as read-write when actually updating. Someone might also want to build packages without installing them. -- Jeremy Maitin-Shepard -- [EMAIL PROTECTED] mailing list
