From: Doug Barton on
On Mon, 19 Jul 2010, RW wrote:

> Am I the only one that thinks it's odd that in 2010 we're still using
> executable scripts to distribute text files?

How would you do it differently?


Doug

--

Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/

Computers are useless. They can only give you answers.
-- Pablo Picasso

_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Anonymous on
Doug Barton <dougb(a)FreeBSD.org> writes:

> On Mon, 19 Jul 2010, RW wrote:
>
>> Am I the only one that thinks it's odd that in 2010 we're still using
>> executable scripts to distribute text files?
>
> How would you do it differently?

$ diff -upNr /nonexistent mynewport

And if you have CVS checkout around

$ cd mycategory
$ cvs add mynewport mynewport/* mynewport/files/*
$ cvs diff -upN mynewport
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Peter Jeremy on
On 2010-Jul-19 02:19:33 +0000, Janne Snabb <snabb(a)epipe.com> wrote:
>On Mon, 19 Jul 2010, Joe wrote:
>
>> This needs to be in the handbook. How is anybody going to know that the
>> `find port_dir` is suppose to be enclosed by [`backticks`]. I has to be said
>> in words not just a printed example.
>
>I would have assumed that anyone who submits a port would be familiar
>with the elementary basics of shell syntax.

The major problems with backticks is that they tend to be inconspicuous
(and easily confused with bits of dust or fly-droppings) and are often
difficult to distinguish from quotes.

Rather than write "`find port_dir` (note the backticks)", IMO, it is
far easier to write $(find port_dir) - which is syntactically the
same but visually more obvious.

--
Peter Jeremy
From: Doug Barton on
On Wed, 21 Jul 2010, Peter Jeremy wrote:

> The major problems with backticks is that they tend to be inconspicuous
> (and easily confused with bits of dust or fly-droppings) and are often
> difficult to distinguish from quotes.
>
> Rather than write "`find port_dir` (note the backticks)", IMO, it is
> far easier to write $(find port_dir) - which is syntactically the
> same but visually more obvious.

That's a fair point. Do you think that the text as it currently exists
is sufficiently clear, or do you think that it still needs the
modification you're suggesting? I'm happy to make the change (or someone
else can if they so desire) if that's what people thing is the right way
to go.


Doug

--

Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/

Computers are useless. They can only give you answers.
-- Pablo Picasso

_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Joe on
Doug Barton wrote:
> On Wed, 21 Jul 2010, Peter Jeremy wrote:
>
>> The major problems with backticks is that they tend to be inconspicuous
>> (and easily confused with bits of dust or fly-droppings) and are often
>> difficult to distinguish from quotes.
>>
>> Rather than write "`find port_dir` (note the backticks)", IMO, it is
>> far easier to write $(find port_dir) - which is syntactically the
>> same but visually more obvious.
>
> That's a fair point. Do you think that the text as it currently exists
> is sufficiently clear, or do you think that it still needs the
> modification you're suggesting? I'm happy to make the change (or someone
> else can if they so desire) if that's what people thing is the right way
> to go.
>
>
> Doug
>
The text as its currently exists is a long way from being clear to a
first timer. And I am talking about the new change that just went in.

"shar `find port_dir` (note the backticks)",

or

"shar $(find port_dir)"

both address the problem nicely.

By all means go and make the correction.


_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"