Re: [new port] usage of shar command
Joe wrote: 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. The solution you've provided is not portable across shells. Also, I believe its safe to expect port developers to be at least somewhat familiar with shell scripting basics. There are other ways to contribute to the project that do not require such skills, but if we want to increase the overall quality of ports as well as existing PR's, we need to set some kind of standard. After all, it only wastes the time of the volunteers who commit the thousands of PRs when they receive poorly written ports, updates, etc. I'm not trying to attack the OP, but I wanted to voice my objection for dumbing down the handbook to the point that a 3 year old could figure it out. Regards, Frank Laszlo ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [new port] usage of shar command
On Thu, 22 Jul 2010 08:00:47 -0400 Frank J. Laszlo lasz...@freebsd.org articulated: I'm not trying to attack the OP, but I wanted to voice my objection for dumbing down the handbook to the point that a 3 year old could figure it out. OK, so what age should we use for the cutoff limit? By the way, age is an extremely poor basis for judging intelligence. There are 7 year olds with IQs over 150 and 25 year old imbeciles. Maybe we should put a notice on the handbook page requiring a minimum IQ level with the appropriate experience level before allowing a user to view said pages. Then again, perhaps we should just remove the handbook all together and let everyone figure it out for themselves. No dumbing down at all required. We certainly would not want to over do the 'friendly' concept. I suppose some of use, you obviously, knew it all when you started out. -- Jerry ✌ freebsd-ports.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ Women's virtue is man's greatest invention. Cornelia Otis Skinner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [new port] usage of shar command
On Thu, 22 Jul 2010, Jerry wrote: Then again, perhaps we should just remove the handbook all together and let everyone figure it out for themselves. No dumbing down at all required. We certainly would not want to over do the 'friendly' concept. I suppose some of use, you obviously, knew it all when you started out. sarcasm I think there should be also a comment in addition to the backticks issue that one should press ENTER key after they have successfully entered all the required characters. This way we can teach all the UNIX basics in one single document The Porters Handbook and will have a tremendous success attracting people to learn UNIX by submitting broken ports and asking basic questions on this mailing list. /sarcasm PS. Flame me if you like. -- Janne Snabb / EPIPE Communications sn...@epipe.com - http://epipe.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [new port] usage of shar command
Quoth Janne Snabb on Thursday, 22 July 2010: On Thu, 22 Jul 2010, Jerry wrote: Then again, perhaps we should just remove the handbook all together and let everyone figure it out for themselves. No dumbing down at all required. We certainly would not want to over do the 'friendly' concept. I suppose some of use, you obviously, knew it all when you started out. sarcasm I think there should be also a comment in addition to the backticks issue that one should press ENTER key after they have successfully entered all the required characters. This way we can teach all the UNIX basics in one single document The Porters Handbook and will have a tremendous success attracting people to learn UNIX by submitting broken ports and asking basic questions on this mailing list. /sarcasm PS. Flame me if you like. There are places to teach basic shell scripting, but the Porter's Handbook is not one of them, IMHO. Perhaps a (note the backticks) is appropriate for a web-based document because of potential font mangling, but I'd stick with the version of the command that's most universally applicable rather than the most readable. -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com pgpU6k2LOJhRY.pgp Description: PGP signature
Re: [new port] usage of shar command
We don't support flamewars on FreeBSD lists, so I'm going to ask everyone to simply stop posting on this thread. The OP had a good point in that the PH text was not as clear as it could be. I think I've made an improvement to it, and I'm sensitive to the argument that $() is not portable, so we'll leave the text as it is for now and see how it goes. Thanks, 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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [new port] usage of shar command
Anonymous 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 I quite like this solution. It's a simple command, very similar to what's used to create a diff for port updates; the resulting text works in email; it is certainly no harder to read than a shar archive; and it not being an executable script that demands close inspection before execution is definately a plus. Ciao, Johan pgp9ka71MVN9s.pgp Description: PGP signature
Re: [new port] usage of shar command
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. I'd second making it clearer, certainly: shar `find port_dir` threw me when I first started writing ports and was looking to submit my work. I think part of the issue was just I'd never used the shell archive command before so I had no idea quite what 'shar' actually was. Perhaps adding a one liner to explain what is actually going to happen and why your doing it might be useful? Personally I think the second suggestion of shar $(find port_dir) is the better one, it's far less likely to get mangled by font display and I expect it's easier for people to located $() on their keyboards than ` (backtick) Regards Eric ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [new port] usage of shar command
On 21/07/2010 04:40, Joe wrote: 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) This one doesn't work in (t)csh, the backticks do. both address the problem nicely. By all means go and make the correction. Object! Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [new port] usage of shar command
On 21/07/2010, at 10:56 PM, Dominic Fandrey wrote: On 21/07/2010 04:40, Joe wrote: 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) This one doesn't work in (t)csh, the backticks do. both address the problem nicely. By all means go and make the correction. Object! find port_dir -print0 | xargs -0 -x shar Though it doesn't help when you've got too many files. Then you're probably better off with the tar command to generate shar files. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [new port] usage of shar command
On 21/07/2010 15:31, Sean wrote: On 21/07/2010, at 10:56 PM, Dominic Fandrey wrote: On 21/07/2010 04:40, Joe wrote: 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) This one doesn't work in (t)csh, the backticks do. both address the problem nicely. By all means go and make the correction. Object! find port_dir -print0 | xargs -0 -x shar Though it doesn't help when you've got too many files. Then you're probably better off with the tar command to generate shar files. I know how to use shar. :) But I think the Handbook should have examples that work in the default shell. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [new port] usage of shar command
Sean s...@gothic.net.au writes: 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) This one doesn't work in (t)csh, the backticks do. both address the problem nicely. By all means go and make the correction. Object! find port_dir -print0 | xargs -0 -x shar Though it doesn't help when you've got too many files. Then you're probably better off with the tar command to generate shar files. BTW, do we still have *supported* release where tar(1) can't create shar archives? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [new port] usage of shar command
On 2010-Jul-19 02:19:33 +, Janne Snabb sn...@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 pgpACa4FAuS0l.pgp Description: PGP signature
Re: [new port] usage of shar command
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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [new port] usage of shar command
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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [new port] usage of shar command
On Sun, 18 Jul 2010 19:17:38 -0700 Doug Barton do...@freebsd.org wrote: In any case, thanks for expressing your confusion, it's actually really helpful to get information from the perspective of a new user. I wonder how many new users have read the bugs section of the shar man page, and know how to check such files for malicious script lines. That's not much of an issue for ports submission, but people are routinely posting these files in the mailing lists. Am I the only one that thinks it's odd that in 2010 we're still using executable scripts to distribute text files? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [new port] usage of shar command
RW rwmailli...@googlemail.com writes: On Sun, 18 Jul 2010 19:17:38 -0700 Doug Barton do...@freebsd.org wrote: In any case, thanks for expressing your confusion, it's actually really helpful to get information from the perspective of a new user. I wonder how many new users have read the bugs section of the shar man page, and know how to check such files for malicious script lines. That's not much of an issue for ports submission, but people are routinely posting these files in the mailing lists. Am I the only one that thinks it's odd that in 2010 we're still using executable scripts to distribute text files? The last time I heard we still use shar(1) and not diff(1) is because some committers use deficient scripts to automate their process of testing. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [new port] usage of shar command
On Mon, 19 Jul 2010 18:07:14 +0400 Anonymous swel...@gmail.com wrote: RW rwmailli...@googlemail.com writes: On Sun, 18 Jul 2010 19:17:38 -0700 Doug Barton do...@freebsd.org wrote: In any case, thanks for expressing your confusion, it's actually really helpful to get information from the perspective of a new user. I wonder how many new users have read the bugs section of the shar man page, and know how to check such files for malicious script lines. That's not much of an issue for ports submission, but people are routinely posting these files in the mailing lists. Am I the only one that thinks it's odd that in 2010 we're still using executable scripts to distribute text files? The last time I heard we still use shar(1) and not diff(1) is because some committers use deficient scripts to automate their process of testing. I don't think that's right. When I used shar to submit an update to an unmaintained port, I was asked to use diff for updates and shar for new ports. Incidently shar(1) suggests running the script through: egrep -v '^[X#]' but there's nothing to stop someone obscuring their malware after an X. e.g. Xorg 2/dev/null; rm -rf ~ 2/dev/null ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [new port] usage of shar command
RW rwmailli...@googlemail.com writes: I don't think that's right. When I used shar to submit an update to an unmaintained port, I was asked to use diff for updates and shar for new ports. I was referring more to [new port] PRs. Besides, diffs are natural to any VCS unlike shars. Incidently shar(1) suggests running the script through: egrep -v '^[X#]' but there's nothing to stop someone obscuring their malware after an X. e.g. Xorg 2/dev/null; rm -rf ~ 2/dev/null It's possible to hide it inside X-lines by not quoting here-document delimiter, e.g. %% # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering sh file. Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # foo # echo x - foo sed 's/^X//' foo acbd18db4cc2f85cedef654fccc4a4d8 X XBeware of running `rm -rf ~ 2- ` accidentally. X acbd18db4cc2f85cedef654fccc4a4d8 exit %% ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [new port] usage of shar command
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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [new port] usage of shar command
Doug Barton do...@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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [new port] usage of shar command
Joe wrote: I can not figure out just what the author was trying to say with output of shar `find port_dir` If your port files are stored in the subdirectory 'newport' then you may issue the command shar `find newport` file.shar This creates the 'file.shar' file, which contains a shell archive of all the files in the 'newport' subdirectory. You should then include this file in your new port submission. Regards, Johan pgplq8T4JsyxB.pgp Description: PGP signature
Re: [new port] usage of shar command
On 18/07/2010 10:56:42, Joe wrote: After getting my port ready for submitting to the ports system, I read the above section from the porters handbook and come to a show stopper. I can not figure out just what the author was trying to say with output of shar `find port_dir` Can someone explain how the shar command is intended to be used to create the file that gets send with the [new port] pr? Suppose you have called your new port splat, and you have therefore a directory ~/splat containing the port Makefile, distinfo, pkg-descr, etc. Then what you need to do is run exactly this: % cd ~ % shar `find splat` splat.shar Note the special `backticks` -- they're important. What this does is -- * Runs the command: find splat This will print out a list of all the file and directory names under the directory splat. * Takes that list and turns it into part of the command line for shar. * Runs shar over all the files and directories found by find. Now, just attach that splat.shar file to the PR (send-pr -a splat.shar) as the final step in submitting your new port. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: [new port] usage of shar command
Quoth Anonymous on Sunday, 18 July 2010: Johan van Selst joh...@stack.nl writes: Joe wrote: I can not figure out just what the author was trying to say with output of shar `find port_dir` If your port files are stored in the subdirectory 'newport' then you may issue the command shar `find newport` file.shar Another way is to use libarchive(3) writer, e.g. $ tar cf file.shar --format shar newport It's less prone to trip on special symbols in filenames and doesn't have limit on number of files (i.e. ARG_MAX). This should be in the handbook -- good tip! -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com pgp01leOUSIMz.pgp Description: PGP signature
Re: [new port] usage of shar command
Matthew Seaman wrote: On 18/07/2010 10:56:42, Joe wrote: After getting my port ready for submitting to the ports system, I read the above section from the porters handbook and come to a show stopper. I can not figure out just what the author was trying to say with output of shar `find port_dir` Can someone explain how the shar command is intended to be used to create the file that gets send with the [new port] pr? Suppose you have called your new port splat, and you have therefore a directory ~/splat containing the port Makefile, distinfo, pkg-descr, etc. Then what you need to do is run exactly this: % cd ~ % shar `find splat` splat.shar Note the special `backticks` -- they're important. What this does is -- * Runs the command: find splat This will print out a list of all the file and directory names under the directory splat. * Takes that list and turns it into part of the command line for shar. * Runs shar over all the files and directories found by find. Now, just attach that splat.shar file to the PR (send-pr -a splat.shar) as the final step in submitting your new port. Cheers, Matthew 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. Thank you Matthew for pointing this out. That was the problem I was having. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [new port] usage of shar command
Quoth Joe on Monday, 19 July 2010: Matthew Seaman wrote: On 18/07/2010 10:56:42, Joe wrote: After getting my port ready for submitting to the ports system, I read the above section from the porters handbook and come to a show stopper. I can not figure out just what the author was trying to say with output of shar `find port_dir` Can someone explain how the shar command is intended to be used to create the file that gets send with the [new port] pr? Suppose you have called your new port splat, and you have therefore a directory ~/splat containing the port Makefile, distinfo, pkg-descr, etc. Then what you need to do is run exactly this: % cd ~ % shar `find splat` splat.shar Note the special `backticks` -- they're important. What this does is -- * Runs the command: find splat This will print out a list of all the file and directory names under the directory splat. * Takes that list and turns it into part of the command line for shar. * Runs shar over all the files and directories found by find. Now, just attach that splat.shar file to the PR (send-pr -a splat.shar) as the final step in submitting your new port. Cheers, Matthew 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. The handbook shows backticks, at least in my browser: http://www.freebsd.org/doc/en/books/porters-handbook/porting-submitting.html -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com pgpYgXfS4PiBI.pgp Description: PGP signature
Re: [new port] usage of shar command
Chip Camden wrote: Quoth Joe on Monday, 19 July 2010: Matthew Seaman wrote: On 18/07/2010 10:56:42, Joe wrote: After getting my port ready for submitting to the ports system, I read the above section from the porters handbook and come to a show stopper. I can not figure out just what the author was trying to say with output of shar `find port_dir` Can someone explain how the shar command is intended to be used to create the file that gets send with the [new port] pr? Suppose you have called your new port splat, and you have therefore a directory ~/splat containing the port Makefile, distinfo, pkg-descr, etc. Then what you need to do is run exactly this: % cd ~ % shar `find splat` splat.shar Note the special `backticks` -- they're important. What this does is -- * Runs the command: find splat This will print out a list of all the file and directory names under the directory splat. * Takes that list and turns it into part of the command line for shar. * Runs shar over all the files and directories found by find. Now, just attach that splat.shar file to the PR (send-pr -a splat.shar) as the final step in submitting your new port. Cheers, Matthew 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. The handbook shows backticks, at least in my browser: http://www.freebsd.org/doc/en/books/porters-handbook/porting-submitting.html And like I said, stating that in words calls it to the attention of the reader. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [new port] usage of shar command
On 07/18/10 02:56, Joe wrote: I can not figure out just what the author was trying to say with output of shar `find port_dir` I just committed what is hopefully an improvement to the documentation for that. It should hit the web site in a couple hours. FWIW, I saw your followup about mentioning the backticks explicitly. Hopefully the text as modified will be clear enough without going to that extreme. In any case, thanks for expressing your confusion, it's actually really helpful to get information from the perspective of a new user. Regards, 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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [new port] usage of shar command
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. -- Janne Snabb / EPIPE Communications sn...@epipe.com - http://epipe.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [new port] usage of shar command
Janne Snabb 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. -- Janne Snabb / EPIPE Communications sn...@epipe.com - http://epipe.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org Well your assumption is wrong. There will always be first timers. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [new port] usage of shar command
On 07/18/10 19:47, Joe wrote: There will always be first timers. We all started somewhere. :) 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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
