revving a dead port
nukama at gmail.com
Sun Oct 14 07:29:43 UTC 2012
On Sun, Oct 14, 2012 at 5:45 AM, Aryeh Friedman
<aryeh.friedman at gmail.com> wrote:
> My company is the original author devel/thistest and we have removed
> the need for the web based download (thus making it buildable)... the
> original maintainer (not us) is long gone and we want to re-release
> the code under a license that allows complete distribution freedom...
> I personally am also the maintainer of devel/aegis and devel/tailor
> but for trivial modifications when taking the port over I have never
> really worked with the port system and need advice on how to make a
> port from scratch
> freebsd-ports at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
You could start from editing the old port, files remain in version control
I test and create ports inside a jail, so that I spot missed dependencies,
you could register at https://redports.org where a clean environment is
used to test a build and also share your preliminary work in subversion.
Fist thing to do - for me - is to make the distfiles fetch-able, so that
I can try to build it from scratch.
Normally I use a Makefile from another similar port and modify
PORTNAME, PORTVERSION, MASTER_SITES and DISTFILES
accordingly while deleting unneeded stuff..
After that I search for needed dependencies and include them in
BUILD_DEPENDS, LIB_DEPENDS and RUN_DEPENDS.
freshports.org has a nice feature, that lets you search for ports
with a dependency on a specific port.
You might follow the link CVSWeb on freshports and look into the
Makefile to copy the right DEPENDS line to your Makefile.
>From this point on it gets specific for each port and I would recommend
to dig into
for further reference.
More information about the freebsd-ports