Hello! I just adopted the rss2email package from unsupported, and I have a small problem. The URL for the source always points to the latest version of the package. It is http://rss2email.infogami.com/rss2email.py In other words, that URL will refer to a new file as soon as a new version is released. What is the preferred solution? I'm tempted to send a nice note to the author, asking for a static URL.
-- Chris
On Sun, Mar 29, 2009 at 09:02:30PM +0200, Chris Brannon wrote:
Hello! I just adopted the rss2email package from unsupported, and I have a small problem. The URL for the source always points to the latest version of the package. It is http://rss2email.infogami.com/rss2email.py In other words, that URL will refer to a new file as soon as a new version is released. What is the preferred solution? I'm tempted to send a nice note to the author, asking for a static URL.
-- Chris
IMO this should be really handled by the author. Static links + maybe something like *-latest.py. Try to poke him :) let's see.
bad, bad practice. shun the unbelievers~
Hello,
On 2009-03-29 at 14:02 -0500 Chris Brannon wrote:
I just adopted the rss2email package from unsupported, and I have a small problem. The URL for the source always points to the latest version of the package. It is http://rss2email.infogami.com/rss2email.py In other words, that URL will refer to a new file as soon as a new version is released. What is the preferred solution? I'm tempted to send a nice note to the author, asking for a static URL.
There are static URLs. Try [1] for example. Using these would be nicer since you wouldn't get warnings about wrong md5sums from makepkg if a newer version is released.
aur-general@lists.archlinux.org