[aur-general] Remove or split?
I have an AUR package (p4v) which installs several binaries for the package. However, Perforce removed a binary and put it in its own installer. I will create an installer for it but what should I do for the p4v installer? Perforce says they remove the binary in their Windows installer. I should probably do the same but I should at least tell them what happened, right? And do I just do an 'rm'? Should I create a so-called split package and install both? I'm loathe to do this, as I for one don't actually use p4sandbox. -- Jonathan Arnold Webstream: http://hieronymus.soup.io Talent wins games, but team work and intelligence wins championships. Michael Jordan
On Fri, 2013-07-19 at 08:05 -0400, Jonathan Arnold wrote:
I have an AUR package (p4v) which installs several binaries for the package. However, Perforce removed a binary and put it in its own installer. I will create an installer for it but what should I do for the p4v installer? Perforce says they remove the binary in their Windows installer. I should probably do the same but I should at least tell them what happened, right? And do I just do an 'rm'?
Should I create a so-called split package and install both? I'm loathe to do this, as I for one don't actually use p4sandbox.
Whatever suits you best, you can create 2 PKGBUILDs, or a single split PKGBUILD. I would do the latter if the binary comes/is built from he same tarball as the rest. If you deem it can be removed altogether, yeah rm will do. Cheers, -- Maxime
participants (2)
-
Jonathan Arnold
-
Maxime Gauduin