2

I'm analyzing different PKGBUILDs to learn creating packages for Arch. I saw in a lot of them, that they do make on sources, and then manually copy files in the different places with the install command, instead of running make install. Is there a reason for it?

Examples:

3

Well for one, these are dkms packages, and the actual make/etc is handled via dkms at install time, not make time.

For another reason, perhaps the Makefile itself is rather shoddy itself and would not work/could not be made to work with arch linux's packaging standards.

If you check out more repo PKGBUILDs you may find more that actually do use make install DESTDIR=${pkgdir}, where ${pkgdir} resolves to the root directory that is tar'd up under fakeroot to set proper permissions during the package() function of the PKGBUILD

  • Most likely the second paragraph :-) – Thomas Dickey Aug 12 '16 at 12:29
  • I just thought about another good reason - explicit list of files that package is adding to my system, that is visible in PKGBUILD, is a nice thing to have :) . – Łukasz Zaroda Aug 12 '16 at 12:53

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.