| 1 |
I wrote a small script that makes spec files unnecessary for stages. |
| 2 |
For GRP, the only thing you need is a package list (shared anyway |
| 3 |
between releases). Same thing for livecds. |
| 4 |
|
| 5 |
http://www.metadistribution.org/gentoo/newrelease.sh |
| 6 |
|
| 7 |
Pieter Van den Abeele |
| 8 |
|
| 9 |
On 11 Jun 2004, at 14:41, Chris Gianelloni wrote: |
| 10 |
|
| 11 |
> On Fri, 2004-06-11 at 00:27, John Davis wrote: |
| 12 |
>> The examples directory in the Catalyst tree is full of a bunch of old |
| 13 |
>> specs, kernel configs, etc. It is taking up space - would anyone mind |
| 14 |
>> if |
| 15 |
>> I cleaned all of that out and replaced it with some well commented |
| 16 |
>> generic specfiles for each Catalyst target? |
| 17 |
>> |
| 18 |
>> Also, I would like to make release specfiles/ kernel configs (and |
| 19 |
>> perhaps even Portage snapshots) available via a Portage ebuild |
| 20 |
>> (gentoo-release-specs perhaps?). We could dictate what is downloaded |
| 21 |
>> by |
| 22 |
>> arch useflag. Any objections? (Thanks to beejay and wolf31o2 for the |
| 23 |
>> suggestion.) |
| 24 |
> |
| 25 |
> I would think catalyst-release-files (or something similar, it just |
| 26 |
> needs the catalyst-* prefix to show it belongs to catalyst) would be a |
| 27 |
> good idea. Also, I think it should install *all* of the .spec/.config |
| 28 |
> files, as someone may want to look into more information on how to |
| 29 |
> build |
| 30 |
> on another platform than the one they are currently running. A good |
| 31 |
> example of this is amd64 and x86, as amd64 can build x86 CDs with |
| 32 |
> minimal trouble (emerging a package). |
| 33 |
> |
| 34 |
> -- |
| 35 |
> Chris Gianelloni |
| 36 |
> Release Engineering QA Manager/Games Developer |
| 37 |
> Gentoo Linux |
| 38 |
> |
| 39 |
> Is your power animal a penguin? |
| 40 |
|
| 41 |
|
| 42 |
-- |
| 43 |
gentoo-releng@g.o mailing list |
Archives