[meego-packaging] Where to store packaging materials?
sivan at omniqueue.com
Tue Aug 31 04:33:41 PDT 2010
2010/8/31 Pertti Kellomäki <pertti.kellomaki at nokia.com>:
> 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
Okay, that made it clearer- so I can think of possibly two ways to address this:
1) Use a full-blown revision control system to record packaging
development; this is exactly what Ubuntu are doing and it works well
in recording, allow for derivations, fixes and wide community
participation in just the packaging process (not the source
- I think this is the ideal.
2) In the lack of (1) , we could probably use to wiki to record and
document packaging development- For example, we could have category
pages per each section and have a directory alphabetized similar to
how a repo is put, with file attachments and so, suboptimal but useful
in recording the work until a public rcs for solely packaging work is
More information about the MeeGo-packaging