[RFC] Repository layout change -- status update

[Patryk Zawadzki]

On 5/15/07, Mariusz Mazur <mmazur at kernel.pl> wrote:
> Ok, after some talks on irc, this is how (the first version of) this solution
> is going to look like:
>
> 'packages' module in our current CVS repo with a flat structure underneath
> consisting of package '%{name}'s. Like this: 'packages/glibc'
> or 'packages/kernel'.
>
> The idea is also to force having spec file names equal to %{name}. Afaik there
> are a few instances where such is not the case.
>
> Afterwards we can have the glob 'packages/%{name}/%{name}.spec' being true
> 100% of the time (might come in handy some day).

AFAIK this is true for all non-kernel packages. Kernel module specs
tend to be named after their tarballs but produce kernel-* packages.

> My proposal goes like this:
>
> have 'packages/%{name}' containt (a) the spec file, (b) a 'files' subdir, that
> contains the traditional 'SOURCES' content and (c) any other files containing
> metadata. Off the top of my head -- the 'tag->revision' file we've discussed
> wrt to svn migration. And in the future -- any other metadata that might
> prove usefull (with the ability to just add a file with some interesting info
> regarding a package, the possibilities are quite big; sooner or later
> someone's bound to use it for builder/ftp/bugzilla/somethingelse
> integration).

+1 for a data subdirectory (the name can be anything from SOURCES to
pink-thongs).

-- 
Patryk Zawadzki
Generated Content