>> >MarsSeed [1] filed a deletion request for wxwidgets-light [2]: >> > >> >Unmaintained since 2023-07-31, and currently several point releases >> >older than repo's wxwidgets (3.2.2.1 vs 3.2.4). >> > >> >But this is also apparently unused, as no one flagged it. >> > >> >And it's not beneficial to keep. This package is not compatible with >> >repo's wxwidgets-gtk3. and therefore most downstream dependent builds >> >cannot use it, e.g. due to its divergent naming of the relevant wx- >> >config executable. >> > >> >But no one complained - again, an evidence of disuse. >> > >> >This also cannot be coinstalled e.g. with repo's veracrypt (which I >> >use). >> > >> >It also builds and puts the headless wxbase into wxwidgets-common- >> >light - another divergence from repo's corresponding package, which >> >does no such thing. >> > >> >Even if configured properly, this build would still break many reverse >> >dependencies - those that need multimedia capabilities - as it omits >> >gstreamer support. >> > >> >Therefore I don't see any benefit in keeping this. Maybe one person >> >(submitter) would disagree, but no one else has shown any indication >> >that they would needs this build. >> > >> >Enough to keep repo's wxwidgets (and AUR's wxwidgets-git). >> > >Zero logs, user not proves what failed. > >of course not install with veracrypt because this package not provide any >support to gstreamer, and is not the intention. if you want use veracrypt, >use [extra] wxwidgets-foo > >greetings
I have have submitted all relevant problem points in my original filing. Cheers
