3 ms·

> This news about cross-platform software. There NO any words in this thread about any Linux packaging issues. >> I'm not sure what it does practically aside

• app4soft 8y ago
  > What you quoted I tell that issue is not only in Linux packaging, but in full changing poject development strategy: moving from "FOSS", to "proprietary+open sourcecode". That's why I asked, what he know about "QCAD & LibreCAD; OpenOffice & LibreOffice" stories. @jchw told that he don't know any reason why Aseprite forked to LibreSprite, other than Linux distribution issue. I give him an answer, that issue with Aseprite was NOT only in Linux packaging, but in changing strategy of original project development (including re-licensing of source code to non-FOSS software). And according that I told that there are already precedents for similar situations -- as result we has now LibreOffice & LibreCAD.
  • vonmoltke 8y ago
    > @jchw told that he don't know any reason why Aseprite forked to LibreSprite, other than Linux distribution issue. That is not at all what the post said. jchw's post (with my annotations): > I purchased Aseprite because it's nice. I'm curious if the author has ultimately benefited from changing the license [of ASEprite], though. I'm not sure what it [making ASEsprite proprietay] does practically aside from that Linux distributions can no longer package it [ASEprite]. Nothing in that post is referring to LibreSprite. jchw is not asking why LibreSprite exists. jchw is asking whether taking ASEprite actually benefitted the author of ASEprite in the long run.