Ottavio Caruso <ottavio2006-netbsd%yahoo.com@localhost> writes: > However I wonder if it is probably better to start from scratch. It is rarely easier to start a package from scratch. The hard part in what you're doing seems to be going over the patches to drop the ones that have been applied upstream or no longer make sense, and to rework the ones that are still needed. (And then file them upstream and put the bugtracker URL in the comment!) > I don't see why we should have two package, one for Abiword and one > for the plugins. They usually come in one single package in other > distributions. The point of splitting packages is to spare people who only want some of them the extra dependencies (or code, but usually it's the dependencies that hurt). If the extra dependency load from plugins is near zero, that may not make sense. > I could reuse the existing makefile.common and enable plugins, and > remove all existing patches. It might probably build, but I am not > sure if the final product would be acceptable for pkgsrc standards. The patches are all there for a reason, or were, at least in theory. The normal thing is to go through them, and this is work. Otherwise all the ones that are still needed are missing, and those issues will resurface. I find that the patch curation is often tedious, but they can be handled one at a time. There really aren't that many, compared to truly scary packages. A lot of them are fixing bashisms. So I could see that job being doable in a few hours. That will leave you with the new problems.
Attachment:
pgp1mnOzEbosz.pgp
Description: PGP signature