Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle split packages #2

Open
musteresel opened this issue May 2, 2013 · 1 comment
Open

Handle split packages #2

musteresel opened this issue May 2, 2013 · 1 comment
Assignees
Labels

Comments

@musteresel
Copy link
Owner

fradeve on Arch forums noticed, that split packages (in his case vim) aren't handled the way it should be.
https://bbs.archlinux.org/viewtopic.php?pid=1242788#p1242788

@ghost ghost assigned musteresel May 2, 2013
@musteresel
Copy link
Owner Author

yaourt is using $pkgbase for itsself, but not to determine whether to call customizepkg or not:

custom_pkg "$pl_pkgname" && customizepkg --modify

where custom_pkg checks for the presence of a file /etc/customizepkg.d/$1.
$pl_pkgname ist the "name" result from pkgquery (http://git.archlinux.fr/package-query.git/tree/doc/package-query.8#n228)

When one would try to build (via abs) vim-runtime from extra, yaourt would call package-query like this:
package-query -1Sif "%r %n %v %a" vim-runtime
The resulting string is (at the moment on my system):
extra vim-runtime 7.3.918-1 x86_64
The second word (space seperated) is then vim-runtime which is taken for $pl_pkgname

So when building vim-runtime from extra yaourt should look for a file /etc/customizepkg.d/vim-runtime

But because it's a split package there is only one PKGBUILD for vim, vim-runtime and gvim.

So to customize THIS pkgbuild one would (check whether this makes sense) need a file for every single package of the split package.

=> Is it better to have customistation for each PKGBUILD or each (binary) package?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant