[aur-general] nanoc3 deletion request
danielwallace at gtmanfred.com
Sat Apr 6 11:51:39 EDT 2013
-----BEGIN PGP SIGNED MESSAGE-----
Xyne <xyne at archlinux.ca> wrote:
>On 2013-04-06 00:25 -0400
>Jeremy Audet wrote:
>>I'm requesting the deletion of the AUR package nanoc3. 
>>The AUR currently includes two similarly-named packages: nanoc and
>>At one time, nanoc provided v2.x of the gem, and nanoc3 provided v3.x
>>the gem.  However, nanoc has supseded nanoc3. If you look at
>>you can see that the two development lines merged from 3.2.0 to 3.3.0.
>>After the release of 3.3.0, nanoc3 releases stopped, whereas nanoc
>>Thus, nanoc3 is no longer being developed, and it has been superseded.
>The package has been merged into ruby-nanoc. Thanks.
>>One last question: assuming the deletion request is approved, should
>>nanoc PKGBUILD both replace() and provide() nanoc3? If I understand
>>correctly, the replace() would allow nanoc3 users a clean upgrade
>>whereas the provide() would allow programs that depend on nanoc3 to
>>nanoc. (new package maintainer here, so still fleshing out my
>Your understanding is correct.
Just remember there is actually no use for replaces in the aur. That directive is only useful in the regular repositories. Provides and conflicts is all you actually need for a clean update.
Replaces is used by pacman to find if there is anything in the repositories that replaces something else. Like when we did all the renames of python packages.
Sent from my Android Phone.
Arch Linux Trusted User
-----BEGIN PGP SIGNATURE-----
Version: APG v1.0.8
-----END PGP SIGNATURE-----
More information about the aur-general