You are not logged in.
- Topics: Active | Unanswered
#1 2008-05-12 14:09:03
- SpookyET
- Member
- Registered: 2008-01-27
- Posts: 410
AUR policy on packages with no version in the source file name
I know that the AUR policy says that no code must be included with the PKGBUILD if you are not a trusted user. But, how do you deal with packages that do not have their version number in the file name: http://www.somesite.com/someproject.tar.gz instead of http://www.somesite.com/someproject-1.0.tar.gz. The problem is that when ''someproject.tar.gz" gets updated, and it will, your AUR package is broken. The MD5 sums won't match and patches may not apply either. You can get around the MD5 problem by not including a MD5 sum, and the package might install correctly if the patches still apply. However, the package version in the PKGBUILD will not match the version of what it installed on disk.
Offline
#2 2008-05-12 14:52:34
- drag0nl0rd
- Package Maintainer (PM)
- From: Czech Republic
- Registered: 2007-10-24
- Posts: 127
- Website
Re: AUR policy on packages with no version in the source file name
You always may upgrade the pkgrel number and update the new MD5 sum. After that, the package isn't the same as before and you see there is a newer version. If the PKGBUILD doesn't work right, you get the feedback on the AUR page in the comments, and can do something about it. Do you have a real package, which behaves like this, or is it a hypotetical question?
Offline
#3 2008-05-12 15:15:48
- SpookyET
- Member
- Registered: 2008-01-27
- Posts: 410
Re: AUR policy on packages with no version in the source file name
I have came across a few. It's not hypothetical at all.
Offline
#4 2008-05-12 15:39:19
- drag0nl0rd
- Package Maintainer (PM)
- From: Czech Republic
- Registered: 2007-10-24
- Posts: 127
- Website
Re: AUR policy on packages with no version in the source file name
So them the pkgrel isn't enough, or does it solve the problem according your needs? I can't see any problem, doing it this way. Or am I missing something?
Offline
#5 2008-05-12 16:25:10
- Stefan Husmann
- Member
- From: Germany
- Registered: 2007-08-07
- Posts: 1,391
Re: AUR policy on packages with no version in the source file name
I have some TeX related packages and it is some kind of politics to not have a pkgver in the filename there. But there are announcements on the certain mailing lists or users complain.
So if the version number is stated in one of the distributed files, I take that. Most of the cases can be solved that way. The remaining cases drag0nl0rd's suggestion is doable.
Offline