Just to clarify things... A couple of minutes ago, I updated the download
URL for qcad (in unstable), due to a report from a user that the previous
URL no longer worked. I assume this is OK, as no recompilation of the
package is necessary?
Yes, that's another instance where you don't
On Tuesday, March 19, 2002, at 11:32 PM, Bertrand Lupart wrote:
Correct me if i'm wrong, but if a user has a foo version of a package
that has obsolete download url, a fink update won't bring him back the
correct download url since the version hasn't been bump versionned.
So he might come
At 17:04 Uhr +1100 16.03.2002, Jeremy Higgs wrote:
On 15/3/02 10:52 PM, David R. Morrison [EMAIL PROTECTED] wrote:
I'd like to remind all core fink developers of the most important rule when
committing things to CVS:
IF YOU HAVE MADE ANY CHANGE TO YOUR PACKAGE, YOU MUST INCREASE THE
Jeremy Higgs [EMAIL PROTECTED] wrote:
Hi David,
Just to clarify things... A couple of minutes ago, I updated the download
URL for qcad (in unstable), due to a report from a user that the previous
URL no longer worked. I assume this is OK, as no recompilation of the
package is necessary?
I'd like to remind all core fink developers of the most important rule when
committing things to CVS:
IF YOU HAVE MADE ANY CHANGE TO YOUR PACKAGE, YOU MUST INCREASE THE
REVISION NUMBER.
Like any good rule, there are exceptions to this: you can modify the
Description field, for example, or
On 15/3/02 10:52 PM, David R. Morrison [EMAIL PROTECTED] wrote:
I'd like to remind all core fink developers of the most important rule when
committing things to CVS:
IF YOU HAVE MADE ANY CHANGE TO YOUR PACKAGE, YOU MUST INCREASE THE
REVISION NUMBER.
Like any good rule, there are
