pkgsrc-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
pkg/30382: update of wm/fvwm2-themes to 0.7.0
>Number: 30382
>Category: pkg
>Synopsis: update of wm/fvwm2-themes to 0.7.0
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: pkg-manager
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Mon May 30 23:06:00 +0000 2005
>Originator: lars nordlund
>Release: 3.99.3
>Organization:
>Environment:
NetBSD ardbeg 3.99.3 NetBSD 3.99.3 (ARDBEG) #0: Wed May 11 09:31:13 CEST 2005
lars@ardbeg:/home/lars/tmp/obj_alpha/sys/arch/alpha/compile/ARDBEG alpha
>Description:
Hello
I have taken the liberty to update fvwm2-themes to the latest
version 0.7.0. Patch is to big to paste into this window. I have put it online
at:
http://www.ludd.ltu.se/~nordlund/fvwm2-themes.0.7.0
One problem though.. When trying it together with fvwm-devel (instead
of fvwm2) I noticed that it did not really work.. The reason is this
line (from the original version of fvwm2-themes/Makefile):
CONFIGURE_ARGS+= --with-ft-datadir=${PREFIX}/share/fvwm2
There is a mismatch between configuration directories in the different
fvwm versions in pkgsrc, and it breaks here. fvwm-devel will use
${PREFIX}/share/fvwm instead of .../fvwm2, which confuses fvwm2-themes.
Since all fvwm variants CONFLICTS with any other fvwm, i.e. it is
not possible to have two installed at the same time, I suggest making
sure that they all use the same directory under ${PREFIX}/share.
Another possibility is to make fvwm2-themes "discover" which fvwm
directory under ${PREFIX}/share to use.. I do not really know how to
implement this in a good way. Or make an PKG_OPTION out of it.. But it feels
clumsy at best..
>How-To-Repeat:
>Fix:
Home |
Main Index |
Thread Index |
Old Index