Re: Right way to build package from non-port software
Catalin Miclaus wrote: Hello guys, What is the right way of building packages for non-ports applications? AFAIK 'make package' and ' pkg_create -b name' are based on ports installed packages. Is there any way of using same commands or additional scripts to achieve similar results? If it matters I'm trying to create packages from net-snmp-5.4.1 sources (needed for 64-bits counters feature) since ports version is based on 5.3.2. Suggestions are welcome. What I would do is: 1. check if there is a PR pending, with an update to the new version; 2. try to adapt the existing port to the new version. Doing 2. should not be much more complicated than building from source, see Porter's Handbook, mainly the ``quick porting'' if you want to do it this way. You do not really need the port infrastructure to use pkg_create, so it seems to be the right tool you were looking for. Hope this helps, -- Michaël ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Right way to build package from non-port software
On Tue, Mar 11, 2008 at 12:38:40AM +0100, Catalin Miclaus wrote: What is the right way of building packages for non-ports applications? AFAIK 'make package' and ' pkg_create -b name' are based on ports installed packages. Is there any way of using same commands or additional scripts to achieve similar results? If it matters I'm trying to create packages from net-snmp-5.4.1 sources (needed for 64-bits counters feature) since ports version is based on 5.3.2. Suggestions are welcome. In this situation, my team generally gets its hands dirty and bumps the port. Usually it's as easy as updating the PORTVERSION variable. Then attach the port diff to a PR and it'll be updated in the official ports tree fast. Unfortunately, net-snmp looks like a pretty complex port that isn't going to be quite so easy. You might consider pinging the maintainer about the new upstream version to see if there's any interest in bumping the port. You might also just be able to write your own port for the new version from scratch (it sounds like you just grabbed the source tarball and didn't apply all the FreeBSD patches). See the handbook [1]. Your best bet may be a combination of the two approaches. [1] http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/quick-porting.html Good luck, -- Chris Cowart Network Technical Lead Network Infrastructure Services, RSSP-IT UC Berkeley pgp4cAyRWxXrN.pgp Description: PGP signature
Right way to build package from non-port software
Hello guys, What is the right way of building packages for non-ports applications? AFAIK 'make package' and ' pkg_create -b name' are based on ports installed packages. Is there any way of using same commands or additional scripts to achieve similar results? If it matters I'm trying to create packages from net-snmp-5.4.1 sources (needed for 64-bits counters feature) since ports version is based on 5.3.2. Suggestions are welcome. BR, Catalin Miclaus Senior Network/Security Administrator ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
