On Wed, Nov 4, 2015 at 5:00 PM, G. Schlisio <g.schli...@dukun.de> wrote:
> > Thanks. I am well aware of AUR packaging. I just hadn't built a package > > with a dependency that is in AUR, not in the repos. > > > > This package is not for me, but for uploading to AUR. > > > > So you are suggesting I use the PKGBUILD of the depdency package as a > > template in my own PKBUILD to build it, then? > > > > Thanks! > > 1) seriously, please bottom post! > > 2) no, i did suggest you to read the wiki page. i am not sure, but i > guess you think there is some kind of difference in package handling > depending on its source - which isnt true. [0] is what you need, > whereever that package will come from. > > [0] https://wiki.archlinux.org/index.php/Pkgbuild#depends > 1) Sorry! Hope it's okay now. Gmail default. 2) "depends" in PKGBUILD doesn't work as the package is only in AUR, causing an error when running makepkg. The package needs libgcrypt11 which is only in AUR. 3) I think some of the language here is a bit unnecessary, like "Just build the damned package, how hard is that?" can be changed to "Just build the package", and "it seems you are bloody new here" can be changed to "it seems you are new here" (BTW: Thanks for the "welcome..." and links etc.). I know how the language usually is on Linux mailing lists, but why should we scare people away. People just gets tired and goes away (other distro or OS) when getting such comments. I'll make my package build the library instead, or add to my wiki page that people should install libgcrypt11 from AUR when installing my package, or else it won't work. I'll prefer the first option, because then only one package would have to be installed. However it will have to conflict with libcrypt11 if the user already has it installed... What do you suggest is the best option? Regards, Ole Jon
