Re: [Xenomai-core] Packaging issues - part 3
Romain Lenglet wrote: This looks like separated issues: fixes of the debian directory may go in the Xenomai svn repository, and cause a debian package update without a new upstream release. But there are maybe other issues ? Alright, but we should be able to make changes in both the Xenomai code and the Debian files, independently. If a package has been released, then if we want to release a new revision of the package that corrects Debian-only issues, then we must be able to ignore any modification in the repository that do not concern the Debian files, to create the new package. We can do that with either separate repositories, or branches in svn. Handling a separate branch mean seems a lot of maintenance, whereas updates of the debian packaging system would go in the debian directory (I mean, except manapges ;-), and work on the trunk would never change the debian directory. Maybe a lighter solution would be to maintain the debian directory at another place in the repository, for example in packages/debian, and to make it appear in trunk using the subversion svn:external attribute. This way the debian directory would appear in all the releases of xenomai. -- Gilles Chanteperdrix.
[Xenomai-core] Packaging issues - part 3
Hi, One more issue about packaging. It is generally a bad idea to make native packages, i.e. to maintain the packaging files (e.g. the debian/* files) into the upstream repository. Some packaging-related issues will arise, such as typos in package docs, file location issues, etc. and releasing packages that correct such issues should not require to make a new upstream release. I therefore propose to make one separate repository for the packaging, for every distribution, and to have separate bug trackers (although Debian already has its own bug tracker for Debian packages), etc. OK, that's all for the weekend... -- Romain Lenglet
Re: [Xenomai-core] Packaging issues - part 3
Romain Lenglet wrote: Hi, One more issue about packaging. It is generally a bad idea to make native packages, i.e. to maintain the packaging files (e.g. the debian/* files) into the upstream repository. Some packaging-related issues will arise, such as typos in package docs, file location issues, etc. and releasing packages that correct such issues should not require to make a new upstream release. This looks like separated issues: fixes of the debian directory may go in the Xenomai svn repository, and cause a debian package update without a new upstream release. But there are maybe other issues ? -- Gilles Chanteperdrix.
Re: [Xenomai-core] Packaging issues - part 3
This looks like separated issues: fixes of the debian directory may go in the Xenomai svn repository, and cause a debian package update without a new upstream release. But there are maybe other issues ? Alright, but we should be able to make changes in both the Xenomai code and the Debian files, independently. If a package has been released, then if we want to release a new revision of the package that corrects Debian-only issues, then we must be able to ignore any modification in the repository that do not concern the Debian files, to create the new package. We can do that with either separate repositories, or branches in svn. -- Romain Lenglet
