[aur-general] Pinning dependency versions in PKGBUILDs?

Stefan Husmann stefan-husmann at t-online.de
Wed Aug 6 13:45:24 EDT 2014

Am 06.08.2014 um 14:31 schrieb Florian Bruhin:
> Hi,
> I'm maintaining the vim-full[1] package which is a vim with all the
> gvim features (Ruby/Lua/Python/Perl/Netbeans) but without GTK/X.
> Now obviously I have to depend on vim-runtime, and I currently I have
> the version number pinned (just like the vim package).
> However that makes upgrading vim-runtime difficult, because pacman
> doesn't know about the vim-full upgrade. A possible solution is to
> build via `makepkg -d` (ignoring the old vim-runtime version), then
> upgrading both vim-full and vim-runtime.
> Should I just not pin the version at all (as in "partial upgrades
> aren't supported anyways") to avoid these problems?
> Florian
> [1] https://aur.archlinux.org/packages/vim-full/
I'd say, regarding pinning keep it as it is.

I have other issues: Built from AUR, this is not an official Arch Linux package, so you should use

--with-compiledby="$PACKAGER"  instead of --with-compiledby='Arch Linux'

(users who do not set PACKAGER in their makepkg.conf will get an empty string, but this is their fault)

And: If this is named -full, it should be full, so also python3 should be supported.

Best Regards


More information about the aur-general mailing list