Hi,
what is the strategy for a repository that is going to have (get) ackages? Those new packages will replace the current stable packages, which is not desired as the new ones are just beta.
Just wondering how others are coping with this.
On 2006-07-28 20:33:53 +0200, Richard Bos wrote:
what is the strategy for a repository that is going to have (get) ackages? Those new packages will replace the current stable packages, which is not desired as the new ones are just beta.
Just wondering how others are coping with this.
i usually append -snapshot or -beta or -unstable to the package name. see runit vs runit-unstable in home:darix dovecot vs dovecot-snapshot in server:mail or lighttpd vs lighttpd-snapshot in ruby.
i usually use the classification from upstream for it.
darix
Op zondag 30 juli 2006 18:07, schreef Marcus Rueckert:
Just wondering how others are coping with this.
i usually append -snapshot or -beta or -unstable to the package name. see runit vs runit-unstable in home:darix dovecot vs dovecot-snapshot in server:mail or lighttpd vs lighttpd-snapshot in ruby.
i usually use the classification from upstream for it.
Thanks a lot for sharing this strategy. I'm going to do this as well.
buildservice@lists.opensuse.org
-
Marcus Rueckert -
Richard Bos