| 1 |
On Mon, 21 May 2007, Petteri Räty wrote: |
| 2 |
|
| 3 |
> > That's what I figured. Okay, last question - how do I stop emerge trying |
| 4 |
> > to update the compiler-less systems to include development tools like gcc? |
| 5 |
> > I presume tweaking the profile is the way to do it. Is there a stock |
| 6 |
> > profile that already has these excluded? |
| 7 |
> |
| 8 |
> I think /etc/portage/profile/package.provided could work. |
| 9 |
|
| 10 |
It looks like it might, but you've got to specify packages with version |
| 11 |
numbers. I could see lots of fun and games when newer versions are added |
| 12 |
to portage or called as dependancies. Keeping this file up to date with |
| 13 |
the version numbers required would make the process rather tiresome. |
| 14 |
|
| 15 |
That said, it's something that could probably be scripted (run a dummy |
| 16 |
emerge on the portage tree and parse the output for any new installs of |
| 17 |
gcc, binutils, etc), and if something did slip through, the corresponding |
| 18 |
binaries shouldn't be on the binhost. |
| 19 |
|
| 20 |
|
| 21 |
-Ronan |
Archives