augmenting a port: request for advice
tmclaugh at sdf.lonestar.org
Sun Dec 9 19:31:45 PST 2007
On Fri, 2007-12-07 at 15:52 -0800, Garrett Cooper wrote:
> On Dec 7, 2007, at 8:03 AM, Stephen Montgomery-Smith wrote:
> > Andriy Gapon wrote:
> >> on 07/12/2007 15:50 Andriy Gapon said the following:
> >>> So I have this solution worth of Solomon's wisdom :-)
> >>> It is to add an option to the port, say with WITH_FUSE. When the
> >>> option
> >>> is turned on the port would download my sources in addition to the
> >>> original sources, then modify the build scripts, patch the original
> >>> sources and build an additional program udfclientfs. Updating
> >>> plist and
> >>> dependencies would also be done, of course.
> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=118484
> >> Please comment.
> > Here is an idea. I notice that the extra sources you want to
> > download are rather small (about 7000 bytes when zipped). How
> > about if you put the sources into the "files" subdirectory of the
> > port itself, and then the port doesn't have to download anything
> > extra.
> > So, for example, the portlint port comes complete with full
> > sources, adding up to nearly 100,000 bytes in its "files"
> > subdirectory. So adding 7000 bytes to a port is going to be small
> > by comparison.
> No dice on that I think. It's artistic license, which means (AFAIK)
> that it can't be distributed with the ports tree as it's not BSD
> licensed code.
The patch itself has a BSD license on it. That said, just because a
patch is not BSD licensed doesn't preclude it from living in the ports
| tmclaugh at sdf.lonestar.org tmclaugh at FreeBSD.org |
| FreeBSD http://www.FreeBSD.org |
More information about the freebsd-ports