Date: Tue, 11 Mar 2008 07:18:30 +0100 From: =?ISO-8859-1?Q?Micha=EBl_Gr=FCnewald?= <michael.grunewald@laposte.net> To: Catalin Miclaus <catalin@starcomms.com> Cc: freebsd-questions@freebsd.org Subject: Re: Right way to build package from non-port software Message-ID: <47D62436.80808@laposte.net> In-Reply-To: <3A0AA7018522134597ED63B3B794C92A0180F1FB@STA-HQ-S001.starcomms.local> References: <3A0AA7018522134597ED63B3B794C92A0180F1FB@STA-HQ-S001.starcomms.local>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47D62436.80808>