[meego-packaging] Where to store packaging materials?

[Pertti Kellomäki]

Hi Sivan,

On 08/31/2010 01:47 PM, ext Sivan Greenberg wrote:
> So you want to share how the package was created, one stage prior to
> the actual source RPM creation? Normally, from my experience this is
> the source package repository, but if that's not detailed enough and
> explanatory enough with the RPM format, then we could try and setup a
> third repo for packaging study?
>    
To put this in concrete terms, here's what I would like to accomplish. 
For packaging meegotouch-applauncherd, I have submitted the following 
files to build.meego.com:

0001-Changes-use-usr-bin-ruby-instead-of-usr-bin-ruby1.8-.patch
meegotouch-applauncherd-0.10.3.tar.bz2
meegotouch-applauncherd.changes
meegotouch-applauncherd.spec
meegotouch-applauncherd.yaml

Now suppose I get assigned to other tasks, and someone else takes over 
the packaging. When it is time to package the next version, the person 
needs to get the files from somewhere. The tar ball obviously comes from 
the meegotouch-applauncherd repository, but what about the other files? 
One can of course grab the source package and extract the files from 
there. However, there is no metadata related to the files (e.g. "why is 
0001-Changes-use-usr-bin-ruby-instead-of-usr-bin-ruby1.8-.patch 
needed?"), and as a mild inconvenience the *.spec file in the source 
archive needs to be refactored back to *.spec and *.changes.

Another possible scenario is that for some reason (e.g. bug hunting) 
someone wants to create an RPM package of some previous version of 
applauncherd. How does one go about finding the files used for packaging 
a particular past version?

I suppose things would be different if build.meego.com were completely 
transparent. My understanding of what OBS can do is still fairly 
limited, but apparently the internal version control system keeps track 
of the packaging materials. However, I don't know of any way to access 
the history without an account at build.meego.com, or to examine 
packages in the development projects for that matter.  I have submitted 
version 0.10.3 to devel:qt-mtf, but as far as I know, the great public 
only sees 0.8.0 which is available in the MeeGo repos.
-- 
Pertti