[makepkg] Question about split packages handling in makepkg

bfo · 2010-05-13 17:32:53

Hello
One question came to my mind, while I was looking at the vlc PKGBUILD. Does splitting packages have to be done in such a non efficient way? I mean, why do we have to delete for example, a directory, once make install has been issued, only to copy the removed parts by hand in the next function? Wouldn't it be better to just specify something like per-package %files section (like in RPM .spec files)? Is this approach possible in Arch without ditching all the work up to now? If there was any discussion about that, I would love to take part in it. I am also looking forward to listening some critical comments.

Allan · 2010-05-13 23:15:51

How is providing a list of files to include more efficient that providing a list not to include?

Anyway, package splitting works a lot better when the upstream Makefile supports installing individual parts. e.g. gcc (somewhat)

bfo · 2010-05-14 09:17:56

Allan wrote:

How is providing a list of files to include more efficient that providing a list not to include?

If it was only about providing a list of files to include/exclude, it would be ok. However, as far as I know, when Makefile has only one install target and we have to separate some files, we have to install all first, and then remove parts which don't fit into the main package just to copy them back in place in the next package-foo2() function. It's like doing the same work twice. Is that right? If so, it could be quite problematic to package bigger projects. I'm kind of speculating here, because I can't name any of the "big projects", but I'm quite sure there are some out there. I hope I made my point clearly now.

tomk · 2010-05-14 09:42:52

Can you indicate where the vlc PKGBUILD does "the same work twice"? I'm looking at it, and what I see is the removal of the browser plugin from the vlc package, and its inclusion in the vlc-plugin package - no duplication of effort, as all this takes place in $pkgdir, not $srcdir. Remember that each split package has its own $pkgdir.

On the contrary, split packaging eliminates duplication of effort by compiling everything for both packages in one build() function.

bfo · 2010-05-14 09:52:52

tomk wrote:

Remember that each split package has its own $pkgdir.

What a terrible mistake of mine. I just misunderstood details of the process. Thank you for explaining.

tomk · 2010-05-14 10:11:12

Welcome - I didn't quite get it at first either.

Arch Linux

#1 2010-05-13 17:32:53

[makepkg] Question about split packages handling in makepkg

#2 2010-05-13 23:15:51

Re: [makepkg] Question about split packages handling in makepkg

#3 2010-05-14 09:17:56

Re: [makepkg] Question about split packages handling in makepkg

#4 2010-05-14 09:42:52

Re: [makepkg] Question about split packages handling in makepkg

#5 2010-05-14 09:52:52

Re: [makepkg] Question about split packages handling in makepkg

#6 2010-05-14 10:11:12

Re: [makepkg] Question about split packages handling in makepkg

Board footer