| 1 |
On 12/17/2012 02:19 AM, Tomáš Chvátal wrote: |
| 2 |
> Currently we put portage into /usr/portage and all related stuff is to |
| 3 |
> be in the subfolders there (distfiles, binpkg). |
| 4 |
> |
| 5 |
> I've always myself override these defaults in make.conf to point for |
| 6 |
> /var/portage/ (not /var/lib because I never bothered enough how to |
| 7 |
> make world and config files to be put elsewhere :P). |
| 8 |
> |
| 9 |
> The only reason why we have this currently in usr is that bsd ports |
| 10 |
> put their stuff in there and I suppose Daniel just did the same. |
| 11 |
> |
| 12 |
> With respect to reality how stuff is done in the linux land all the |
| 13 |
> variable data should be in /var so we should adjust and move it in |
| 14 |
> there too. |
| 15 |
> |
| 16 |
> What would you think? |
| 17 |
|
| 18 |
I like the idea. As noted in bug #378603 [1], I'd like the portage |
| 19 |
ebuild to ensure that the locations don't unexpectedly change for |
| 20 |
existing installs. |
| 21 |
|
| 22 |
Will it break catalyst? If so, we might begin the migration by fixing |
| 23 |
catalyst and having to set the new default locations in the make.conf |
| 24 |
that it generates. |
| 25 |
|
| 26 |
[1] https://bugs.gentoo.org/show_bug.cgi?id=378603#c1 |
| 27 |
-- |
| 28 |
Thanks, |
| 29 |
Zac |
Archives