[opensuse-buildservice] How to use aggregate and merge updates?
I built syslogd, first against openSUSE:11.0 repo, and second against openSUSE:11.0:Update repo. The build logs show that in the first case, libacl was taken from the distribution version, and in the second case, from the newer version in update. The :Update repo says "Use this repository only if you need to compile against incompatible update releases ... kmp modules." I think I also read somewhere that non kernel packages are guaranteed compatible. But what if I want to build against the updates anyway? It seems I can't aggregate my packages to the :Update repo, because aggregate does not work if there is no update for a package. So what is the best approach for using aggregate and merging updates into my project, so I can re-release it from time to time? I also need to use link and patch some packages, so I don't think KIWI is the right place to start. -- Webmail for Dialup Users http://www.isp2dial.com/freeaccounts.html -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2008-11-15 18:03:26 +0000, John Kelly wrote:
I built syslogd, first against openSUSE:11.0 repo, and second against openSUSE:11.0:Update repo.
The build logs show that in the first case, libacl was taken from the distribution version, and in the second case, from the newer version in update.
The :Update repo says "Use this repository only if you need to compile against incompatible update releases ... kmp modules." I think I also read somewhere that non kernel packages are guaranteed compatible.
There are some rare cases where this "rule" doesn't apply (e.g. kmps, clamav...).
But what if I want to build against the updates anyway?
It seems I can't aggregate my packages to the :Update repo, because aggregate does not work if there is no update for a package.
Hmm why don't you build directly against the Update repo? You could also build against openSUSE:XXX and openSUSE:XXX:Update. I think there's no need to you an aggregate.
So what is the best approach for using aggregate and merging updates into my project, so I can re-release it from time to time?
I also need to use link and patch some packages, so I don't think KIWI is the right place to start.
I'm no kiwi expert but I think you can also use kiwi with your linked packages. Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Sat, 15 Nov 2008 19:21:36 +0100, Marcus Hüwe
It seems I can't aggregate my packages to the :Update repo, because aggregate does not work if there is no update for a package.
Hmm why don't you build directly against the Update repo? You could also build against openSUSE:XXX and openSUSE:XXX:Update. I think there's no need to you an aggregate.
I want more from OBS than just building a few custom packages against various repos. My goal is to track a minimal subset of packages from a distribution and merge the updates. Base:build is similar to what I want, but it tracks factory, and I don't want factory bugs. I want to track a stable distro, and I want updates merged. And, I want to hack some packages the way I like. So for 80% of packages I could use aggregate, and for 20% I could use link. For aggregate, I want the updates automatically, I don't want to search for them myself. But with link, I will review all changes to any package I patched locally. And I want to backport select packages from factory, on a special case basis, where I believe no bugs will bite. I just wonder why no one else has already done this. I suppose SLE is similar, but I want to roll my own small subset of packages, and do it my way. -- Webmail for Dialup Users http://www.isp2dial.com/freeaccounts.html -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (2)
-
John Kelly -
Marcus Hüwe