| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Hello, |
| 5 |
|
| 6 |
I've recently activated the buildpkg feature in the hope that if |
| 7 |
anything goes wrong (I'm using the testing branch ;) ) I'll have working |
| 8 |
versions of the necessary packages to repair the system stockpiled. |
| 9 |
|
| 10 |
However this obviously means that quite a lot of packages are produced, |
| 11 |
which takes up lots of diskspace eventually. |
| 12 |
|
| 13 |
What I'm wondering is if there is any plan to make buildpkg more |
| 14 |
configurable? For example either the ability to remove the previous |
| 15 |
archive of a package when a new one is created, or better yet, a way to |
| 16 |
specify that binary packages should only be created for system packages |
| 17 |
and their dependencies, not for the entire world? |
| 18 |
|
| 19 |
The worry that I'm trying to remove is that one day something will |
| 20 |
happen that will a) damage the installation and b) damage the ability of |
| 21 |
the system to repair itself (gcc, python, portage etc..). This already |
| 22 |
happened to me once during the upgrade from GCC2 to GCC3 (due to a |
| 23 |
mistake on my part) and I ended up doing a full reinstall, which is a pain. |
| 24 |
|
| 25 |
Cheers, |
| 26 |
|
| 27 |
Andy |
| 28 |
-----BEGIN PGP SIGNATURE----- |
| 29 |
Version: GnuPG v1.2.1 (GNU/Linux) |
| 30 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 31 |
|
| 32 |
iD8DBQE+IZQRX3TTUvZURBERAhJIAJ9gie5yXnCKEO/O1dOOeZ4zB2Mv7ACdETm5 |
| 33 |
bJjbOLJCN0f3Qvi5wV7pdhM= |
| 34 |
=oZMx |
| 35 |
-----END PGP SIGNATURE----- |
| 36 |
|
| 37 |
|
| 38 |
-- |
| 39 |
gentoo-dev@g.o mailing list |
Archives