Requirements gathering for new package source control

[Christoph Höger]

Am Dienstag, den 10.06.2008, 15:23 -0400 schrieb Jesse Keating:
> On Tue, 2008-06-10 at 21:16 +0200, Christoph Höger wrote:
> > I just had another idea (correct me, when thats already possible -
> > again):
> > How about some kind of automagic spec file generation for the versioning
> > part? Some kind of every commit/branch gets its own Version header
> > generated, that would easily allow every possible assertion on how
> > versioning information shall be handled.
> 
> This somewhat possible now, I think the kernel package has done
> something like this in the past.  It makes the spec file look like soup
> though, and not very friendly to those that want to base their work off
> your spec file outside our source control.  Personally I'd rather stay
> away from source control magic making it's way into the specfiles.
> 
> -- 
> fedora-devel-list mailing list
> fedora-devel-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list

Then the obvious solution would be to create a meta-spec file and let
whoever wants to (which would include SCM) create a specific specfile
from that.

This could have even more advantages like some kind of inheritance (you
could use generic "java packages" or "autoconf packages") or automagic
selinux policy creation from meta informations. 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://lists.fedoraproject.org/pipermail/devel/attachments/20080610/691a6dab/attachment.bin