| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 12/18/2012 02:49 PM, Rick "Zero_Chaos" Farina wrote: |
| 5 |
> On 12/18/2012 01:38 PM, Zac Medico wrote: |
| 6 |
>> On 12/17/2012 02:19 AM, Tomáš Chvátal wrote: |
| 7 |
>>> Currently we put portage into /usr/portage and all related stuff is to |
| 8 |
>>> be in the subfolders there (distfiles, binpkg). |
| 9 |
>>> |
| 10 |
>>> I've always myself override these defaults in make.conf to point for |
| 11 |
>>> /var/portage/ (not /var/lib because I never bothered enough how to |
| 12 |
>>> make world and config files to be put elsewhere :P). |
| 13 |
>>> |
| 14 |
>>> The only reason why we have this currently in usr is that bsd ports |
| 15 |
>>> put their stuff in there and I suppose Daniel just did the same. |
| 16 |
>>> |
| 17 |
>>> With respect to reality how stuff is done in the linux land all the |
| 18 |
>>> variable data should be in /var so we should adjust and move it in |
| 19 |
>>> there too. |
| 20 |
>>> |
| 21 |
>>> What would you think? |
| 22 |
> |
| 23 |
>> I like the idea. As noted in bug #378603 [1], I'd like the portage |
| 24 |
>> ebuild to ensure that the locations don't unexpectedly change for |
| 25 |
>> existing installs. |
| 26 |
> |
| 27 |
>> Will it break catalyst? If so, we might begin the migration by fixing |
| 28 |
>> catalyst and having to set the new default locations in the make.conf |
| 29 |
>> that it generates. |
| 30 |
> |
| 31 |
>> [1] https://bugs.gentoo.org/show_bug.cgi?id=378603#c1 |
| 32 |
> |
| 33 |
> Yes, it will break catalyst. However, if the folder that the portage |
| 34 |
> tree goes in is still something/something/portage then it shouldn't be |
| 35 |
> hard to fix. |
| 36 |
> |
| 37 |
It should probably be mentioned (since most of us don't use the |
| 38 |
snapshots every day) that the snapshots actually contain a folder called |
| 39 |
"portage" in the tarball. Not that it would be impossible to change, |
| 40 |
but if we migrate from /usr/portage to /var/whatever/portage then the |
| 41 |
changes are trivial, if we migrate to /var/repositories/gentoo that |
| 42 |
makes things like unpacking the snapshots significantly non-trivial. |
| 43 |
|
| 44 |
I really don't care what everyone wants to do here (although I'm |
| 45 |
generally for sticking closer to FHS), but I warn that if the path |
| 46 |
doesn't end in "portage" the changes are going to be significantly |
| 47 |
non-trivial. |
| 48 |
|
| 49 |
Thanks, |
| 50 |
Zero |
| 51 |
|
| 52 |
> -ZC |
| 53 |
> |
| 54 |
|
| 55 |
-----BEGIN PGP SIGNATURE----- |
| 56 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 57 |
Comment: Using GnuPG with undefined - http://www.enigmail.net/ |
| 58 |
|
| 59 |
iQIcBAEBAgAGBQJQ0MwqAAoJEKXdFCfdEflKF0YQAJ1mBkAPgDcIdXL+2eIdc5GO |
| 60 |
yk7t2qSOtSaU159C8d2xI2AdB3b5jm5AXWrrvpAovNIAMTN/fFa781oKQVkFprsS |
| 61 |
AZsT3UFluLep3ngLVTvpv8nry2t0AhT+/k1u1GAeurnTT5b4GDGXu7EF+QHzeaLC |
| 62 |
+8VF8/N0TvRp+PwZ9lEJGXd+RVXxQ6AJXo1XsIbgKnA/L5mCKCfYn3o+9oQCqHbW |
| 63 |
fPVeGyqEAKVYFG8rNUHwxPHYUvxhIC7xxuBl81ErXv5VqhcgNNjX4SMnKXeT3Z/V |
| 64 |
FRxtnLJMz69mlX9C+CMf9boFVfveMjGj7pZOzopJGGhJM3d8Q/rAbgHejEmtrlAd |
| 65 |
n9FBLc7ihGGBGGcTHrmhG+1DalmY/c2WaR63NfR+Le5mIpPpC0mibhK5TYeWRAcF |
| 66 |
zFJhjmLwBfyAlBLnQk6gd4x/c8jMH68wgvRqPNMJbWETkT3tntgl7cUcoesv6TdT |
| 67 |
fGNuISGCqMSEHHTKxX9XvqBl5EDSNEIS4I7rbFwO3qtuHuR2+88H506E9RQU4Xdd |
| 68 |
+/bV6EW3Z7s/9hp7LhvK5CqEXAfJwN278aJOKAuyNX/YmwKa1VXy/ZDMXEUrTa6x |
| 69 |
r+LcgyNHUkY3Sr4OFR7yoIY/oH4FrP1Y5H45GQUNje/XeL7bnLoN9h4QfeIwwt/L |
| 70 |
6KZZtj3hmJa7I/m5hBwv |
| 71 |
=VeR7 |
| 72 |
-----END PGP SIGNATURE----- |
Archives