On Sat, 16 Oct 2010 16:09:21 +0200 Dave Plater wrote:

For what it's worth I use the last release version number plus svn revision when I package svn snapshots ie. last release = 1.20 then an svn snapshot from svn rev 748 will become 1.20.748 then the release 1.21 is > 1.20.748.

Fortunately the project uses git, so no revision numbers ;-)

If the final release of your "0.9.25beta17" is 0.9.25 there might be a problem because I suspect that the beta version is greater than the release version and you will have to use provides and obsoletes or something.

That's why I want to package the 0.9.25betaX as 0.9.24.99.nnnn I'll probably go for 0.9.24.99.17 for the beta17 and 0.9.24.99.17.$(DATE) for potential later snapshots. beta18 will become 0.9.24.99.18 and will be bigger. Cristians "zypper vcmp" hint is a good one - I did not know that feature ;-) Thanks, seife -- Stefan Seyfried "Any ideas, John?" "Well, surrounding them's out." -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

On 10/17/2010 03:02 AM, Cristian Rodríguez wrote:

El 16/10/10 20:04, Stefan Seyfried escribió:

...

On Sat, 16 Oct 2010 16:09:21 +0200 Dave Plater wrote:

...

For what it's worth I use the last release version number plus svn revision when I package svn snapshots ie. last release = 1.20 then an svn snapshot from svn rev 748 will become 1.20.748 then the release 1.21 is> 1.20.748.

Fortunately the project uses git, so no revision numbers ;-)

I use this versioning scheme for projects using git:

I have a wrapper script, called "mkgitsnap"

cat ~/bin/mkgitsnap #!/usr/bin/env bash

DATE=$(date --universal +%Y%m%d%H%M)

NAME=$1

VERSION=$2

git archive --prefix=${NAME}-${VERSION}_git${DATE}/ HEAD | xz -9 > ${NAME}-${VERSION}_git${DATE}.tar.xz

then, in your .gitconfig

[alias] ... snap = !mkgitsnap

the in the git cloned repo, run

git snap <appname> <version> where version is the latest released version.

Should work just fine.

Good idea, I already extract svn revisions with my wip svn snapshot scripts, I'll adapt your idea to them. Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

On 10/17/2010 02:22 PM, Cristian Rodríguez wrote:

El 17/10/10 04:49, Dave Plater escribió:

...

Good idea, I already extract svn revisions with my wip svn snapshot scripts, I'll adapt your idea to them. Dave P

Better if you share them with us ;-)

ATM I'm still learning to master sed but when I have something workable I'll definitely show it off. Gota keep the ego going somehow. Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

On Sun, Oct 17, 2010 at 4:58 PM, Cristian Rodríguez wrote:

El 17/10/10 10:37, Dave Plater escribió:

...

ATM I'm still learning to master sed but when I have something workable I'll definitely show it off. Gota keep the ego going somehow. Dave P

It doesnt have to be perfect, we can put all this tools in a git repository and improve them overtime.

Currently people are providing, even the most trivial stuff this way, including configuration files, there is no reason to be shy ;-)

Hello, what I'm currently using for generating packages from SVN can be found for instance in this package home:bmanojlovic:games/orxonox I put in spec file information from "svn info http://svn.repo/project" into rpm .spec file enclosed between separators # SVN_INFO_START and # SVN_INFO_END so you can immediately see which revision is used looking into .spec file script that i use can be seen at home:bmanojlovic:games/orxonox/download_latest_svn P.S. "Scriptlet" for making git snapshot is nice one ;) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

On 10/17/2010 06:27 PM, Cristian Rodríguez wrote:

El 17/10/10 12:42, Boris Manojlovic escribió:

...

P.S. "Scriptlet" for making git snapshot is nice one ;)

I just improved it a bit, now it uses the "last commit" date as reference date and not the current time, and also sets tarball mtime accordingly.

#!/usr/bin/env bash

GIT_DATE=$(git log HEAD -n 1 --format=%cD) DATE=$(date --universal +%Y%m%d%H%M -d "${GIT_DATE}")

NAME=$1

VERSION=$2

git archive --prefix=${NAME}-${VERSION}_git${DATE}/ HEAD | xz -9 > ${NAME}-${VERSION}_git${DATE}.tar.xz touch -c -t "${DATE}" ${NAME}-${VERSION}_git${DATE}.tar.xz

hth.

So far I've an updaterg.sh and updateblen.sh for svn rosegarden4-10.06 (I'll start using svn revisions in the version after 10.06 is released for now I put the revision in the spec file under description and summary) it's more stable than the current release. Here's updaterg.sh : #!/bin/bash rm -rf /data/src/osc/rosegarden-10.06 svn export /data/src/rosegarden /data/src/osc/rosegarden-10.06 pushd /data/src/osc/ tar -acf rosegarden-10.06.tar.bz2 rosegarden-10.06 mv rosegarden-10.06.tar.bz2 /data/src/osc/home:plater/rosegarden-qt4/rosegarden-10.06.tar.bz2 popd cat /data/src/rosegarden/.svn/entries|grep -m1 -b1 dir It's tailored for my own directory structure which is /data/src is where svn, cvs, bzr and git local copies reside. Then we have /data/src/osc with my buildservice stuff and also used for working on svn export source. I have to put in a couple of options and a bit of sed to automatically update the spec file. Also would be nice to select revisions via option. Regards Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org