[gentoo-releng] catalyst examples dir

[gentoo-releng] catalyst examples dir

[John Davis]

[-- Attachment #1: Type: text/plain, Size: 776 bytes --]

Hi all -
The examples directory in the Catalyst tree is full of a bunch of old
specs, kernel configs, etc. It is taking up space - would anyone mind if
I cleaned all of that out and replaced it with some well commented
generic specfiles for each Catalyst target?

Also, I would like to make release specfiles/ kernel configs (and
perhaps even Portage snapshots) available via a Portage ebuild
(gentoo-release-specs perhaps?). We could dictate what is downloaded by
arch useflag. Any objections? (Thanks to beejay and wolf31o2 for the
suggestion.)

Cheers,
-- 
John Davis
Gentoo Linux Developer
<http://dev.gentoo.org/~zhen>

----
GnuPG Public Key: <http://dev.gentoo.org/~zhen/zhen_pub.asc>
Fingerprint: 4F9E 41F6 D072 5C1A 636C  2D46 B92C 4823 E281 41BB

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-releng] catalyst examples dir

[Donnie Berkholz]

[-- Attachment #1: Type: text/plain, Size: 477 bytes --]

On Fri, 2004-06-11 at 00:27, John Davis wrote:
> Also, I would like to make release specfiles/ kernel configs (and
> perhaps even Portage snapshots) available via a Portage ebuild
> (gentoo-release-specs perhaps?). We could dictate what is downloaded by
> arch useflag. Any objections? (Thanks to beejay and wolf31o2 for the
> suggestion.)

I think it'd make more sense to include kernel configs with the kernel
ebuilds themselves.
-- 
Donnie Berkholz
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-releng] catalyst examples dir

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 1203 bytes --]

On Fri, 2004-06-11 at 00:27, John Davis wrote:
> The examples directory in the Catalyst tree is full of a bunch of old
> specs, kernel configs, etc. It is taking up space - would anyone mind if
> I cleaned all of that out and replaced it with some well commented
> generic specfiles for each Catalyst target?
> 
> Also, I would like to make release specfiles/ kernel configs (and
> perhaps even Portage snapshots) available via a Portage ebuild
> (gentoo-release-specs perhaps?). We could dictate what is downloaded by
> arch useflag. Any objections? (Thanks to beejay and wolf31o2 for the
> suggestion.)

I would think catalyst-release-files (or something similar, it just
needs the catalyst-* prefix to show it belongs to catalyst) would be a
good idea.  Also, I think it should install *all* of the .spec/.config
files, as someone may want to look into more information on how to build
on another platform than the one they are currently running.  A good
example of this is amd64 and x86, as amd64 can build x86 CDs with
minimal trouble (emerging a package).

-- 
Chris Gianelloni
Release Engineering QA Manager/Games Developer
Gentoo Linux

Is your power animal a penguin?

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-releng] catalyst examples dir

[Pieter Van den Abeele]

I wrote a small script that makes spec files unnecessary for stages. 
For GRP, the only thing you need is a package list (shared anyway 
between releases). Same thing for livecds.

http://www.metadistribution.org/gentoo/newrelease.sh

Pieter Van den Abeele

On 11 Jun 2004, at 14:41, Chris Gianelloni wrote:

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


--
gentoo-releng@gentoo.org mailing list