| 1 |
Neil Bothwick <neil <at> digimed.co.uk> writes: |
| 2 |
|
| 3 |
|
| 4 |
> > I'm not sure how to put everything dev-java into a set; so that |
| 5 |
> > it will updated but not depclean out those packages. |
| 6 |
|
| 7 |
> A set can be simply a list of packages in a file in /etc/portage/sets. |
| 8 |
|
| 9 |
|
| 10 |
Ok so I created this file (644): |
| 11 |
/etc/portage/sets/dev-java |
| 12 |
|
| 13 |
I put a list of file in there, here are a few: |
| 14 |
dev-java/log4j |
| 15 |
dev-java/xpp2 |
| 16 |
dev-java/xpp3 |
| 17 |
dev-java/jaxme |
| 18 |
java-virtuals/stax-api |
| 19 |
<snip> |
| 20 |
|
| 21 |
I tried all sorts of --depclean syntax variants but it did not protect the |
| 22 |
files listed in the file from removal. I modified my make.conf like so: |
| 23 |
|
| 24 |
EMERGE_DEFAULT_OPTS="--exclude gentoo-sources @dev-java " |
| 25 |
|
| 26 |
|
| 27 |
Now every rendition of depclean usage just wants to remove these files. |
| 28 |
It feels like there is a working mechanism here, but I'm struggling |
| 29 |
to find the exact method to protect these files from depclean, not identify |
| 30 |
them form deep cleansing. What am I missing? |
| 31 |
|
| 32 |
|
| 33 |
|
| 34 |
James |
Archives