Mailinglist Archive: opensuse-buildservice (181 mails)
| < Previous | Next > |
Re: [opensuse-buildservice] How to name stable, development and edge packages?
- From: Marcus Rueckert <mrueckert@xxxxxxx>
- Date: Wed, 11 Jul 2007 19:33:10 +0200
- Message-id: <20070711173310.GA5578@xxxxxxx>
On 2007-07-11 19:08:49 +0200, Lars Marowsky-Bree wrote:
> we (as in, Andrew and myself for the Linux HA project) maintain
> server:ha-clustering packages, in particular heartbeat.
>
> Now, for that, Andrew maintains a stable build which we're actually
> recommending to users, and I do a daily build in my home project, build
> with some scripts from Andrew's because _link isn't powerful enough.
_link can do patching of the source tree. so i dont see what is stopping
you here. you can patch spec/changes files and all that.
> I'd like to make that more "official" and move it out of my playground.
>
> Is there already a naming convention for that?
>
> 1) I could add them to server:ha-clustering as heartbeat-snapshot, plus
> obsoletes/provides lines. I think that would be kind of ugly.
no obsoletes.
but i dont see why it would be ugly? it works pretty well for
dovecot(-snapshot), lighttpd(-snapshot). see the spec file how to keep
the maintenance work low.
> 2) I could create a new project to build them, which wouldn't be quite
> as ugly, but then - what to name it?
>
> I like 2) best and would like to suggest we create a (CURRENT|DEVEL)
> top-level distinction, because I don't think we're the only ones with
> this issue. Then user's would automatically know where to go look for
> the development snapshots.
i dont like the idea of having such namespace. current doesnt always
mean unstable. a subproject or a package as in 1) are better options
imho.
darix
--
openSUSE - SUSE Linux is my linux
openSUSE is good for you
www.opensuse.org
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
> we (as in, Andrew and myself for the Linux HA project) maintain
> server:ha-clustering packages, in particular heartbeat.
>
> Now, for that, Andrew maintains a stable build which we're actually
> recommending to users, and I do a daily build in my home project, build
> with some scripts from Andrew's because _link isn't powerful enough.
_link can do patching of the source tree. so i dont see what is stopping
you here. you can patch spec/changes files and all that.
> I'd like to make that more "official" and move it out of my playground.
>
> Is there already a naming convention for that?
>
> 1) I could add them to server:ha-clustering as heartbeat-snapshot, plus
> obsoletes/provides lines. I think that would be kind of ugly.
no obsoletes.
but i dont see why it would be ugly? it works pretty well for
dovecot(-snapshot), lighttpd(-snapshot). see the spec file how to keep
the maintenance work low.
> 2) I could create a new project to build them, which wouldn't be quite
> as ugly, but then - what to name it?
>
> I like 2) best and would like to suggest we create a (CURRENT|DEVEL)
> top-level distinction, because I don't think we're the only ones with
> this issue. Then user's would automatically know where to go look for
> the development snapshots.
i dont like the idea of having such namespace. current doesnt always
mean unstable. a subproject or a package as in 1) are better options
imho.
darix
--
openSUSE - SUSE Linux is my linux
openSUSE is good for you
www.opensuse.org
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
| < Previous | Next > |