Unifont mess

fstirlitz · 2014-08-04 09:11:09

Hi. I've had a split GNU Unifont PKGBUILD in the AUR for some time, which separately packages Unifont in all formats and the accompanying utilities. Before the AUR update which added support for split packages, it appeared under the name "unifont". After updating the package, I've got a naming conflict with both the official bdf-unifont in [extra] and other Unifont packagers in AUR.

My wish would be for my PKGBUILD to replace the official Unifont package. What do I do?

Lone_Wolf · 2014-08-04 10:25:37

simplest solution seems to be to use another pkgbase, like unifont-felix .

The subpackages could then get lines like these (example for ttf-unifont-felix ) :

provides = ("ttf-unifont")
conflicts = ("ttf-unifont")

Check 'man PKGBUILD' or https://wiki.archlinux.org/index.php/PKGBUILD for details about provides/conflicts .

fstirlitz · 2014-08-04 15:36:55

Lone_Wolf wrote:

provides = ("ttf-unifont")
conflicts = ("ttf-unifont")

bash: syntax error near unexpected token `('

And I already do this anyway. My problem is that the same thing is packaged five times, and it needn't be. While my PKGBUILD packages everything already, and even adds a few extra bits. Whom do I ask to resolve this?

Lone_Wolf · 2014-08-05 11:33:54

I've compared the bdf-unifont & your PKGBUILDS, and it looks like you download the full package, whereas the bdf-unifont package only installs that font.

Best option is to contact the maintainer of bdf-unifont, their emailaddy is in the PKGBUILD.

Arch Linux

#1 2014-08-04 09:11:09

Unifont mess

#2 2014-08-04 10:25:37

Re: Unifont mess

#3 2014-08-04 15:36:55

Re: Unifont mess

#4 2014-08-05 11:33:54

Re: Unifont mess

Board footer