Ottavio Caruso <ottavio2006-netbsd%yahoo.com@localhost> writes: > I have looked on the pkgsrc guide and the wip guide but I have only > found answers on how to create a package from scratch, so here it is. > > Let's say there is a package in pkgsrc whose version is 0.9. The > package is not strictly obsolete because it might still receive > updates, however it's a bit too old. In the meantime the package > version from mainstream has gone to 2.7. > > How could a simple user attempt to make a new package based on the > newer version? Should they reuse the existing makefile and hack it a > little bit and see if that works, or should they make a new package > from scratch, as described on the pkgsrc guide? I would advise updating the existing bits. Sometimes it's just changing the version number. If the upstream build system hasn't changed, then it might work or you might need to change the PLIST. It's almost always easier to modify than start over, and it's preferred. Definitely set PKG_DEVELOPER=yes and run pkglint when doing this. > And if the build works, should they upload it to wip or notify the > maintainer or eventually also one of the mailing lists? Any of the following are reasonable: put the new version in wip email maintainer with diff and commit message (changes since version in pkgsrc proper) and state what testing you've given it email pkgsrc-users file a PR and maybe email somebody about it Generally, if it's obvious the update should happen and it's not complicated, email is good. If it's much more complicated, and others helping debug the new package would help, wip is good, because other people can just fix things leading to more rapid convergence. Usually situations where updates are overdue are just because no one has gotten to it. If there's a reason not it should be in the makefile. But always good to ask the MAINTAINER if there is one (and especially if there is an OWNER, but those tend to be looked after much more thoroughly). Hope this helps!
Attachment:
pgpAXy2lJyOGp.pgp
Description: PGP signature