Hombre, calmate! Democracy is no applicable concept in light of technical requirements!
If fsviewer doesn't compile anymore due to some easily curable lack on wmaker's behalf, then this is rather good practice IMHO. Upstream is a moving target, and distribution packagers have to adapt to some degree. And while we are at it, since the removal of include/WINGs, wmmail doesn't compile anymore. They are still available in Debian with the old libwings-dev 0.92.0 package. I had to added these old includes from libwings-dev to the wmmail source package to be able to at least compile it. If someone cares, the full debian sources for wmmail are included on the wmlive ISO image in the top level folder dockapps/sources. Cheers Paul On 02/26/2012 11:40 PM, Rodolfo García Peñas wrote: > > I spent a lot fo mails with this topic, because the debian packages problem. > You, and only you say "NO", and now, you restore it? > > What should I do now? re-create a libwmaker0-dev package? > > My english is so bad to explain my feelings, but... "with two eggs!!" (1) > > Anyway, probably you should send things to wmaker-dev before apply it, and be > more "democratic" > > kix > > (1) Con dos cojones!! > > --8<-- > Add wmlib folder back > > It was removed on 67a8a826703507bebad2 with the assumption that > nothing was using it. But that was not really the case - FSViewer > used it. > > I've just tested it. After a trivial fix regarding the change in > the function definition of WMWritePropListToFile(), FSViewer > compiles and even seems to work (didn't test much though). > > So let's not be unfair with FSViewer and put wmlib back. FSViewer > might even be used for educational purposes for people wanting to > write apps using WINGs etc. > > > -- To unsubscribe, send mail to [email protected].
