* [email protected] <[email protected]> schrieb:
> I can see some value in this approach as there are now almost too many
> music and multimedia distros to choose from. A lot of the work is being
> replicated and with varying results. It makes the overall platform seem
> unstable and it must be frustrating for new users or users who don't want
> to spend time working on installation issues before they can start
> producing.
ACK. That's one of the reasons why I founded the OSS-QM project.
IMHO the first thing we should do is importing the packages with
their local changes into git (turn dpatch files into direct commits)
and then create the debian-patch from this.
So the history of an imported debpkg release would look like this:
-> [upstream-release] <- tag:
UPSTREAM.$pkg-$version
-> dpatch #0
...
-> remaining direct changes (w/o ./debian/) <- tag:
64STUDIO-SRC.$pkg-$version
-> applying ./debian/ (w/ dpatches already removed) <- tag:
64STUDIO-DEB.$pkg-$version
I'll see if I can hack someting up that automates this.
Later releases (when directly maintained in git) would be rebased
to the following upstream releases and fixes done in git. Right
before the final deb-release, the branch gets sorted/refined
(interactive rebase, etc) so that the ordering described about
remains intact.
If the upstream has some public vcs w/ (maybe via automatic mirrors,
like those I'm maintaining on pubgit.metux.de) w/ proper tagging,
its tags should be directly used as upstream (or maybe adding the
release tarball as a intermediate commit).
I'll see if I hack up some automatic robot ...
BTW: feel free to join oss-qm: https://sourceforge.net/p/oss-qm/home/
cu
--
----------------------------------------------------------------------
Enrico Weigelt, metux IT service -- http://www.metux.de/
phone: +49 36207 519931 email: [email protected]
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666
----------------------------------------------------------------------
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------
_______________________________________________
64studio-devel mailing list
[email protected]
http://lists.64studio.com/mailman/listinfo/64studio-devel
