cvs commit: ports/textproc Makefile ports/textproc/ack Makefile distinfo pkg-descr pkg-plist

Sahil Tandon sahil at FreeBSD.org
Tue Aug 9 22:34:01 UTC 2011


On Tue, 2011-08-09 at 15:25:09 -0700, Doug Barton wrote:

> On 08/09/2011 15:01, Sahil Tandon wrote:
> > On Tue, 2011-08-09 at 21:16:23 +0100, Chris Rees wrote:
> > 
> >> On 9 August 2011 20:43, Doug Barton <dougb at freebsd.org> wrote:
> >>> On 08/09/2011 12:18, Chris Rees wrote:
> >>>> On 9 August 2011 17:50, Steven Kreuzer <skreuzer at freebsd.org>
> >>>> wrote:
> >>>>> I missed it when I first looked to see if this was a port. I
> >>>>> removed mine from the tree
> >>>>>
> >>>>
> >>>> Would anyone object if I looked at adding danfe's grep suggestion
> >>>> to addport ? We have similar checks in rmport...
> >>>
> >>> Not sure exactly what you're proposing. If you're talking about
> >>> humans looking to see if a port exists already then 'cd /usr/ports
> >>> && make search name=foo' is probably an easier way to do that.
> >>
> >> I was thinking of (like the PRs open for $port of rmport)
> >>
> >> Ports named like ack: textproc/p5-ack
> >>
> >> Are you sure you wish to continue [Y/N]?
> > 
> > I think this is a reasonable idea - please do not be discouraged from
> > trying.
> 
> I sincerely hope you're not referring to my question as a possible
> source of discouragement.

Nope!

> It certainly was not intended to be.

Understood.

> I agree that this kind of functionality is a good addition to addport,
> the only questions are "What is the best way to accomplish it?" and
> "Might there be a more generally useful approach?"

Agreed on both, hence my mention of useful implementation.  Once there
is pseudo-code or an initial patch to illustrate crees' thinking, I hope
we can collectively answer the two questions you pose above.

-- 
Sahil Tandon <sahil at FreeBSD.org>


More information about the cvs-ports mailing list