Am 04.11.2015 um 17:52 schrieb Ole Jon Bjørkum:
On Wed, Nov 4, 2015 at 5:46 PM, Levente Polyak <anthraxx@archlinux.org> wrote:
No, please don't even try to, just add the depends() and thats it.
Ok, then that's it. Just trying to improve the AUR here guys, correcting my package after a complaint that my package's .install script did some stuff it shouldn't.
I'll also add to my package wiki that users should install libgcrypt11 from AUR first to make it as easy as possible for newbies.
Martti Kühne: Very mature. Please read my previous post about the language here. Trying to be polite here.
Regards, Ole Jon
ok, i'll try to explain. you seem to have a whole bunch of misconceptions about archlinux, the aur and packaging, and try to work around arising problems. working around problems is good. what is annoying people here is that you seem not to see they point you at your misconceptions. i believe, you could resolve them by reading a good part of the wiki, so i suggested a starting point. your basic misunderstanding is about how aur packages interact. basically, makepkg is not responsible for resolving dependencies - the user is. what you are trying is to make makepkg do something it isnt supposed to do. many peoble use aur helpers (see [0]), which handle dependencies for them. others do it by hand. but makepkg is never in charge of that. you could build a package with the --nodeps option, which makes makepkg omit dependency resolving and just yields you a package. [0] https://wiki.archlinux.org/index.php/AUR_helpers