Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 09 Dec 2007 22:31:42 -0500
From:      Tom McLaughlin <tmclaugh@sdf.lonestar.org>
To:        Garrett Cooper <youshi10@u.washington.edu>
Cc:        Stephen Montgomery-Smith <stephen@math.missouri.edu>, Andriy Gapon <avg@icyb.net.ua>, freebsd-ports@freebsd.org
Subject:   Re: augmenting a port: request for advice
Message-ID:  <1197257502.9694.3.camel@tomcat.straycat.dhs.org>
In-Reply-To: <B16E66A6-EE5B-4475-8D03-CD5EBB48D7A2@u.washington.edu>
References:  <47594FAB.8050804@icyb.net.ua> <47596C80.8030905@icyb.net.ua> <47596EE1.3070606@math.missouri.edu> <B16E66A6-EE5B-4475-8D03-CD5EBB48D7A2@u.washington.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
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.
> -Garrett

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
tree.

tom


-- 
| tmclaugh at sdf.lonestar.org                 tmclaugh at FreeBSD.org |
| FreeBSD                                       http://www.FreeBSD.org |




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1197257502.9694.3.camel>