On Wed, Mar 31, 2010 at 8:48 PM, Arjan van de Ven <[email protected]> wrote: > On 3/31/2010 22:24, Julian Andres Klode wrote: >> >> On Wed, Mar 31, 2010 at 10:09:31PM +0300, Arjan van de Ven wrote: >>> >>>> But normal tarballs are better anyway for distributions wanting >>>> to package parts of MeeGo for their own use. >>> >>> but distributions wanting to package stuff also need the patches etc... >>> they can just rpm2cpio the src.rpm's..... much more complete. >> >> That would be repackaging, not packaging. > > no it's extracting the source and patches from the src.rpm > into a directory.
And in a lot of cases the patches in the rpm are distro specific to deal with the libraries or disto specific bits so may well not be needed by others. >> And furthermore, >> I am talking about software maintained by MeeGo; for which >> there should be no patches but only releases. And source >> tarballs are handier than extracting them from srpms > > theory and practice may be different things. Even though meego engineers > may be upstream maintainers for some of these projects, there can and > will be situations where the distribution team needs to put a temporary > patch in/ How does that relate to tar file releases. That's the case with all tar releases being built in distros dependant on other surrounding bits in the distro that's being dealt with whether it be libraries or other distro specific things. The patches will change from distro to distro and even release to release. That doesn't mean there shouldn't be a base tar file release to base all on. From the Meego perspective I would have thought having a base version that bugs can be reported against would be easier for tracking of issues across distros rather than random points in a git repo. Peter _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
