You are not logged in.

#1 2007-04-16 00:00:01

skottish
Forum Fellow
From: Here
Registered: 2006-06-16
Posts: 7,942

Versionpkg modification

I'd like to have a modification of versionpkg that names packages with date format. For instance, if one builds FFMPEG from subversion, instead of it being named ffmpeg-svn, it would be called ffmpeg-20070415. That way the package will pass validation tests, i.e. VLC requires 'ffmpeg>=20070131'.

Offline

#2 2007-04-16 05:57:23

pressh
Developer/TU
From: Netherlands
Registered: 2005-08-14
Posts: 1,719

Re: Versionpkg modification

I'm perfectly happy with the packages beining called -svn, -cvs, -git, etc. There was a discussion a while ago about having all the -svn, -cvs and a like packages named to something like -dev, -devel or something else, but that proposal didn't make it I believe.
I like things being called as they are, so a package from subversion should be named likewise -svn. That really is not a problem in validation tests, as long as you provide the needed provides and conflicts in the PKGBUILD.

Also from a date you can't see if things have changed in subversion, so a package build two weeks ago can still be the latest

Offline

#3 2007-04-16 08:40:09

tomk
Forum Fellow
From: Ireland
Registered: 2004-07-21
Posts: 9,839

Re: Versionpkg modification

skottish wrote:

That way the package will pass validation tests, i.e. VLC requires 'ffmpeg>=20070131'.

You may be confusing things here. The minimum version requirement given in your VLC example validates against the pkgver of the package it depends on, so in this case VLC needs ffmpeg, minimum version 20070131. You're suggesting that the date becomes part of pkgname, where it could not be validated.

Offline

#4 2007-04-16 12:42:40

skottish
Forum Fellow
From: Here
Registered: 2006-06-16
Posts: 7,942

Re: Versionpkg modification

tomk wrote:

The minimum version requirement given in your VLC example validates against the pkgver of the package it depends on, so in this case VLC needs ffmpeg, minimum version 20070131. You're suggesting that the date becomes part of pkgname, where it could not be validated.

I worded the request wrong. My apologies. I need the package version to be named after the date, not the package itself.

Offline

#5 2007-04-16 20:16:38

sl
Banned
From: uk
Registered: 2007-04-04
Posts: 42
Website

Re: Versionpkg modification

correct me if i'm wrong,
but i don't realyl see what the problem is here. ..

http://www.archlinux.org/packages/537/

...p -Ss ffmpeg
extra/ffmpeg 20070131-1
...

Offline

#6 2007-04-16 20:36:56

skottish
Forum Fellow
From: Here
Registered: 2006-06-16
Posts: 7,942

Re: Versionpkg modification

Programs like FFMPEG (that was just one example of programs I use) are improving nearly daily, and do not have "release" builds. There are many projects that are starting to go this way. The FFMPEG version listed above (which has now fixed A/V sync issues) is a subversion snapshot by a developer. I'm simply trying to take a couple of steps out of building programs that I update at least weekly. If no one sees this as being a good idea, just let the thread die, and I'll figure it out.

Offline

#7 2007-04-17 12:44:06

sl
Banned
From: uk
Registered: 2007-04-04
Posts: 42
Website

Re: Versionpkg modification

umm, well have you considerd puttign it in yourself?
maybe this will help ...

`date +%G%m%d`
~[pkgver=`^`]~
`man date`

Offline

#8 2007-04-17 15:59:59

skottish
Forum Fellow
From: Here
Registered: 2006-06-16
Posts: 7,942

Re: Versionpkg modification

Thanks sl. The solution that I ended up with is to write a script that pulls the subversion sources into a directory, change a custom pkgbuild to update to the current date (`date +%Y%m&d`), and run makepkg. I haven't implemented it yet, but it seems fairly straight forward.

Last edited by skottish (2007-04-17 16:53:39)

Offline

Board footer

Powered by FluxBB