![](https://seccdn.libravatar.org/avatar/28c510cf31d0e67caf01e9b438d7b6a3.jpg?s=120&d=mm&r=g)
On Mon, 17 Sep 2012 23:36:19 +0100 Nelson Marques <nmo.marques@gmail.com> wrote:
Dear all,
I have a simple question; Let's imagine we have a package 'foobar'; which the latest stable release is 1.0. Someone decides to to update to git snapshot and uses a version based on the date, for example: 20121017, where the NEVRA goes into something like:
Name: foobar Epoch: 0 Version: 20121017 Release: 0 Arch: noarch
Now after two years of git snapshotting we get an official release, lets say, 1.1; Would it normal to suppose that version wise:
20121017 > 1.1
Eventually my guess was that we should enforce Epoch to get back into track and make sure 1.1 would replace the former packages; If I understood correctly it is not wise to use Epoch within openSUSE and it should be banned...
So... How do we get this update going ?
This is just an hipotetical case, though I can remember of few examples currently in production, which don't for this case; I'm mainly interesting in knowing how to deal with this in openSUSE.
Thanks.
NM Hi AFAIK It should be related to the git/svn etc release, for example for gimp-dds I used;
date_rXXX So using export; svn export -r175 http://gimp-dds.googlecode.com/svn/trunk/ gimp-dds So it became latest stable release+svnyyyymmdd_r175 in the version. The version should always prefix in your case something like 1.0+gityyyymmdd_rabcdefg Then 1.1 would be greater, even if it's 0.0 then you would still see it updated.... -- Cheers Malcolm °¿° (Linux Counter #276890) openSUSE 12.2 (x86_64) Kernel 3.4.6-2.10-desktop up 7:31, 6 users, load average: 0.08, 0.11, 0.13 CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org