On Aug 13 2007 10:02, Adrian Schröter wrote:
>On Monday 13 August 2007 09:57:27 wrote Marcus Meissner:
>> Hi,
>>
>> I am getting occasional request to keep stable Wine
>> versions for some of the older releases.
>>
>> Is there a mechanism that would allow that?
>
>In general you have two options:
>
>1. You could build multiple versions of the same package. You can do this by
> creating multiple packages in the build service in one project. For example
> you create a "wine-1.0" package and a "wine-2.0" package.
> Inside of these workspaces, you can still use "wine.spec", which produces
> a wine-1.0-0.i386.rpm and a wine-2.0-0.i386.rpm. The Build Service does not
> remove old versions, if the src.rpm does still get build.
>
> While this works nicely with the build service, your users might run into
> trouble since their used installer might want to update to 2.0, even when
> they do not want this.
>
>2. To solve this, you can simply create another project, like "Wine:OLD" to
> get a separated repository on our servers.
3. Maybe it's possible to do configure --prefix=/opt/wine-2.0 and then have
wine1 and wine2 installed side-by-side on a system.
Jan
--
