| 1 |
On Fri, 2004-06-11 at 00:27, John Davis wrote: |
| 2 |
> The examples directory in the Catalyst tree is full of a bunch of old |
| 3 |
> specs, kernel configs, etc. It is taking up space - would anyone mind if |
| 4 |
> I cleaned all of that out and replaced it with some well commented |
| 5 |
> generic specfiles for each Catalyst target? |
| 6 |
> |
| 7 |
> Also, I would like to make release specfiles/ kernel configs (and |
| 8 |
> perhaps even Portage snapshots) available via a Portage ebuild |
| 9 |
> (gentoo-release-specs perhaps?). We could dictate what is downloaded by |
| 10 |
> arch useflag. Any objections? (Thanks to beejay and wolf31o2 for the |
| 11 |
> suggestion.) |
| 12 |
|
| 13 |
I would think catalyst-release-files (or something similar, it just |
| 14 |
needs the catalyst-* prefix to show it belongs to catalyst) would be a |
| 15 |
good idea. Also, I think it should install *all* of the .spec/.config |
| 16 |
files, as someone may want to look into more information on how to build |
| 17 |
on another platform than the one they are currently running. A good |
| 18 |
example of this is amd64 and x86, as amd64 can build x86 CDs with |
| 19 |
minimal trouble (emerging a package). |
| 20 |
|
| 21 |
-- |
| 22 |
Chris Gianelloni |
| 23 |
Release Engineering QA Manager/Games Developer |
| 24 |
Gentoo Linux |
| 25 |
|
| 26 |
Is your power animal a penguin? |
Archives