On 2020/12/03 15:45, Michael wrote:
> Hello ports,
> 
> first of all I initially overlooked that there was already an attempt to 
> bring fvwm to 2.6.9 [0] in April. The 2.6.7 port update was done 
> independent of that and since 2.6.7 is still marked as the "stable" 
> version [1] I would prefer that version for now. There is also another, 
> older version labeled as LTS, however as I understand it this only keeps 
> some ancient modules alive. Should those really be needed there is 
> always the version from base. Furthermore there is already fvwm3 [2] but 
> since it is not marked as stable (I think) and also will break 
> compatibility with fvwm2 config files some day, I suggest treating this 
> as a different subject.

that would probably be better done as x11/fvwm3

> I would also like to add pledge() to the most common modules, but I 
> assume this should better be done with an extra patch and therefore is 
> not included here.

btw: pledge can be quite a pain when you're dealing with libraries
from ports - it can be done if the programs and libraries involved are
simple, but you can't expect somebody updating a library to figure out
all the possible interactions with pledge that might occur due to the
update.

> Notable changes:
> * Project moved to github
> * Updated DESCR
> * Removed multipackage since the icon package is gone
...
> +@conflict fvwm2-*

you don't want this ^^

> +@conflict fvwm95-*

and this is long dead

> +@conflict fvwm2+fvicons-*
> +@conflict fvicons-*

those two are ok

you're also missing these

@pkgpath x11/fvwm2,-main
@pkgpath x11/fvwm2,-fvicons
@pkgpath x11/fvwm2,-fvwm2

and these in quirks $stem_extensions

                'fvwm2+fvicons' => 'fvwm2',
                'fvicons' => 'fvwm2',

to test the update path, fix the above and build packages including a
new quirks package. move those package files to a directory on their own.
install the old package/s from a snapshot and point pkg_add at them:

        PKG_PATH=/tmp/fvwmpkgs pkg_add -D unsigned -ui

test with the various versions of the old package.

(the old stuff was a complicated set of alternatives, more akin to
what FLAVORS would do, they aren't a typical multipackage).

Reply via email to