Arch Linux User Repository

@eugene2k These dependencies are part of the base-devel group and are assumed to be installed when using makepkg. Please refer to the ArchWiki for more information.

This needs autotools and automake in the dependencies list

Ah, ok. Makes sense (although I would argue a bit different in case of downgrading) And yes, noextract would be a solution, but personally I stick with an additional commit locally for this repo.

@TrialnError That is a valid point of view but I prefer to stick as close to upstream as possible. Furthermore this allows for using the same PKGBUILD for different GTK versions which might ease downgrading (supported as long as no partial updates are done). I would recommend you either specifying makepkgs's PURGE_TARGETS and using purge or pacman's NoExtract option depending on whether you want a custom package or just want to install a 'normal' package differently.

As in Arch is only the latest stable release available, I suppose the Paper versions for specific gtk versions could be removed from the package (namely 3.0, 3.16, 3.18)

Please don't flag this package as out-of-date if it is properly building! The PKGBUILD honors the VCS guidelines [1] and therefore the pkgver is generated on build time. Simply rebuilding the package is sufficient to get the latest version. Either way I updated the pkgver and uploaded it. (@wadeowen) [1] https://wiki.archlinux.org/index.php/VCS_package_guidelines

@stefan_vgapass Thanks for beeing an attentively user, however your assumption here is false. Clearly automake [1] is a dependency to create this package, though it should NOT be added to the makedepends array. Members of the base-devel group are already expected to be installed [2] when using makepkg and automake is just one of those packages. Please make yourself familiar with the corresponding ArchWiki entries to understand the Arch packaging standards. Btw. the comma "," serves no purpose in the shell array concerning your excerpt. @helmi77 You recently flagged this package as out-of-date. Please don't do so! The PKGBUILD honors the VCS guidelines [3] and therefore the pkgver is generated on build time. Simply rebuilding the package is sufficient to get the latest version. Either way I uploaded a new version, since my last push was about a month ago. [1] https://www.archlinux.org/packages/core/any/automake/ [2] https://wiki.archlinux.org/index.php/PKGBUILD#makedepends [3] https://wiki.archlinux.org/index.php/VCS_package_guidelines

@edh Thanks for maintaining this package ! The PKGBUILD is missing automake as a makedepends dependency. The build needs to use aclocal ( part of the automake pkg ). The current way the PKGBUILD file is setup (7ecb1e8c05c5420f0ad93fe1f39f3adc00f46454) with only git in the makedepends list makes the makepkg build fail: ``` makedepends=('git') ``` This is the updated makedepends list that would enable me to install the paper-gtk-theme-git pkg without any issues. ``` makedepends=('git', 'automake') ``` In my case I've just installed automake to make the build work.

@TrianInError I guess it is best to treat both gtk versions as optdepends. Thanks for the hint.

Isn't gtk-engine-murrine just an optdepend? As it is just needed for the gtk2 theme.