| 1 |
On Tue, 8 Aug 2017 20:15:07 +0200 |
| 2 |
Kristian Fiskerstrand <k_f@g.o> wrote: |
| 3 |
|
| 4 |
> On 08/08/2017 08:10 PM, William L. Thomson Jr. wrote: |
| 5 |
> >> I'm not sure explicitly about environment files, but it's an |
| 6 |
> >> option to emerge. For instance, I've added this to my |
| 7 |
> >> EMERGE_DEFAULT_OPTS to ensure none of the following are built: |
| 8 |
> >> |
| 9 |
> >> --buildpkg-exclude "virtual/* sys-kernel/*-sources dev-perl/* |
| 10 |
> >> perl-core/*" |
| 11 |
> > Something like this would NOT be desirable. It would have to be |
| 12 |
> > done on every system. |
| 13 |
> It would have to be set on every binhost, not every client system.. |
| 14 |
> that said, I prefer env approach as it is easier to track changes |
| 15 |
> properly in a CVS |
| 16 |
|
| 17 |
That is assuming clients do not have FEATURES="buildpkg". I have that |
| 18 |
set just in case I merge some package directly on a system. I have the |
| 19 |
binary ready for others. I am trying out the env route now, but may |
| 20 |
need some changes there. |
| 21 |
|
| 22 |
Most are made on the binhost, but not all. Also I am not necessarily |
| 23 |
using a binhost per se. I have portage on shared NFS. I also rsync some |
| 24 |
binaries between NFS servers. |
| 25 |
|
| 26 |
-- |
| 27 |
William L. Thomson Jr. |
Archives