[aur-general] Remove vimperator-git
I am the maintainer of "vimperator-git". That project now uses mercurial (hg) rather than git, so I have uploaded a new package named "vimperator-hg", and now I would like to have "vimperator-git" removed from AUR. Thanks! mfwitten P.S. Under the current conventions, it is necessary to change the package name whenever the underlying version control system (VCS) is changed. Perhaps there should be a policy that encourages a more general suffix for such packages: "vimperator-vcs".
Michael Witten wrote:
I am the maintainer of "vimperator-git". That project now uses mercurial (hg) rather than git, so I have uploaded a new package named "vimperator-hg", and now I would like to have "vimperator-git" removed
Done!
P.S. Under the current conventions, it is necessary to change the package name whenever the underlying version control system (VCS) is changed. Perhaps there should be a policy that encourages a more general suffix for such packages: "vimperator-vcs".
That's an interesting idea. Personally, I like it. I doubt that Joe User (or Jane User) typically cares about the VCS used by a given project. -- Chris
On Tue, Oct 27, 2009 at 12:15 PM, Michael Witten <mfwitten@gmail.com> wrote:
I am the maintainer of "vimperator-git". That project now uses mercurial (hg) rather than git, so I have uploaded a new package named "vimperator-hg", and now I would like to have "vimperator-git" removed from AUR.
Thanks! mfwitten
P.S.
Under the current conventions, it is necessary to change the package name whenever the underlying version control system (VCS) is changed. Perhaps there should be a policy that encourages a more general suffix for such packages: "vimperator-vcs".
I guess my `replaces=(vimperator-git)' took care of it. :-) I was wondering whether that would happen; I guess I should have checked.
Michael Witten wrote:
I guess my `replaces=(vimperator-git)' took care of it. :-)
I was wondering whether that would happen; I guess I should have checked.
No, I did. You can't cause packages to be deleted automatically just by putting them in the "replaces" array. Imagine how easy it would be to abuse a (mis)feature like that! -- Chris
On Tue, Oct 27, 2009 at 12:39 PM, Chris Brannon <cmbrannon79@gmail.com> wrote:
Michael Witten wrote:
I guess my `replaces=(vimperator-git)' took care of it. :-)
I was wondering whether that would happen; I guess I should have checked.
No, I did.
Ah! :-) That's more believable.
You can't cause packages to be deleted automatically just by putting them in the "replaces" array. Imagine how easy it would be to abuse a (mis)feature like that!
It depends on the rules that define who and when something can be deleted. The current AUR policies are bizarre to me: The AUR is a sink for any old package, and the only way to unclog it is to contact the town plumber. Can't we give the village folk some tools to handle their own minor maintenance issues? In this case, as the maintainer of both packages (vimperator-{git,hg}), it wouldn't seem unreasonable to allow me to replace one package with another. In particular, why not at least allow a maintainer to deprecate a package; anyone else can un-deprecate a package, and after a while (say, a couple of months), if nobody has un-deprecated a deprecated package, then that package should be deleted automatically---or at least someone with the power to delete the package should be notified to do so. How about automatically marking a package as deprecated (as described above) if the package files haven't been accessed in some interval of time (say, a year). Also, how about automatically removing the maintainer of a package if that package has been marked out-of-date for some interval of time (say, a couple of months). Just some ideas (that probably aren't new). Thanks, mfwitten
On Tue, Oct 27, 2009 at 6:26 PM, Michael Witten <mfwitten@gmail.com> wrote:
Under the current conventions, it is necessary to change the package name whenever the underlying version control system (VCS) is changed. Perhaps there should be a policy that encourages a more general suffix for such packages: "vimperator-vcs".
I guess my `replaces=(vimperator-git)' took care of it. :-)
I was wondering whether that would happen; I guess I should have checked.
BTW replaces only has an effect when put in a sync db for pacman. So it is completely useless on AUR, at least from pacman point of view, but I am not aware of any other usage of this field. You can only use provides/conflicts
On Tue, Oct 27, 2009 at 12:46 PM, Xavier <shiningxc@gmail.com> wrote:
BTW replaces only has an effect when put in a sync db for pacman. So it is completely useless on AUR, at least from pacman point of view, but I am not aware of any other usage of this field. You can only use provides/conflicts
Yeah... the docs are a little inscrutable, providing only a description of the tangential result:
replaces (array) An array of packages that this package should replace, and can be used to handle renamed/combined packages. For example, if the j2re package is renamed to jre, this directive allows future upgrades to continue as expected even though the package has moved. Sysupgrade is currently the only pacman operation that utilizes this field, a normal sync will not use its value.
In fact, I'm pretty sure that the last sentence was added fairly recently.
participants (3)
-
Chris Brannon
-
Michael Witten
-
Xavier