1 |
Does anyone know of an existing way in which to not include development |
2 |
related files in binary package builds, so as to generate packages that would |
3 |
be more apprpriate for a server? |
4 |
|
5 |
Case in point, I have an NFS server that neither builds it's own packages nor |
6 |
does it have any use for any headers or static libraries (or even gcc for |
7 |
that matter). I can manually remove stuff from /usr/include, /usr/lib/*.a, |
8 |
etc but next round of upgrades and all the dev related files would be back, |
9 |
so it would be very handy to generate packages that did not have the files to |
10 |
begin with. |
11 |
|
12 |
From what I've seen, I have a few current options: |
13 |
|
14 |
1) custom ebuilds - this would be a bit of a management nightmare |
15 |
2) system imager - in progress, but I would rather have the control at the |
16 |
package level since the "golden client" would still need to be fixed. |
17 |
3) scripts that clean files after package installs - again, it would be nice |
18 |
not to have any files to clean rather than to delete them after the fact. |
19 |
|
20 |
Any of these is do-able in one context or another, but they still remain as a |
21 |
way to override what is installed with a package, rather than remedying the |
22 |
package itself. |
23 |
|
24 |
Does anyone have something more elegant or perhaps know of tools that can |
25 |
control the contents of a binary package without having to manually manage |
26 |
the ebuild? |
27 |
|
28 |
TIA |
29 |
|
30 |
Mike Culbertson |