Re: FAO: cfg: defaults
On Sat, 4 Jan 2003, Randall R Schulz wrote: John, At 08:50 2003-01-04, John Morrison wrote: ... Please find for you perusal and review... (long links, will wrap!) Why don't you enclose all URLs in email within angle brackets instead of forcing people to reintegrate the wrapped links? Even a short URL can fall on a line wrap boundary if embedded in other text. Didn't know I could! :) Thanks for the tip, will do in future. J. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: FAO: cfg: defaults
On Sat, Jan 04, 2003 at 07:32:50PM -0800, Randall R Schulz wrote: I hope this isn't too far off-topic or excessive in its protractedness. If you'd like, I'll tease the cat a little and get some scratches on my arms. Mrrow! I do appreciate the education. Thanks. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: FAO: cfg: defaults
On Sat, Jan 04, 2003 at 03:36:12PM -0500, Christopher Faylor wrote: You don't need my permission. Just post to cygwin-apps and see what others think. Or, since you're the package maintainer and, I'm sure that you've tested this, feel free to just refresh your packages. Actually, I do have one comment. If you are using incver_ifdep in setup.hint then you should name the package something like foo-01-1.tar.bz2. The 01 part gets updated every time there is a package which relies on it. To rephrase that: The 01 part gets incremented every time a package is updated or created which relies on the other criteria in the setup.hint. cgf
Re: FAO: cfg: defaults
On Sat, Jan 04, 2003 at 04:50:41PM -, John Morrison wrote: From: Christopher Faylor On Mon, Dec 02, 2002 at 12:56:03PM -, Morrison, John wrote: You'd probably want something like: snip/ setup.hint: sdesc: Conditionally move default files to proper location category: _PostInstallLast requires: ash findutils fileutils sed sh-utils autodep: etc/defaults/.* incver_ifdep: yes This would run automatically whenever packages are downloaded and installed in one shot. It wouldn't run if someone downloads everything and then installs piecemeal, though. I think there are lots of things that don't work when cygwin is not installed via setup. I can't think of any other way... The script to move the files would be the only thing in the package and it would be a post-install script. Done :) Please find for you perusal and review... (long links, will wrap!) http://homepage.ntlworld.com/j-n-s.morrison/john/cygwin/update-defaults/upda te-defaults-1.0-.tar.bz2 http://homepage.ntlworld.com/j-n-s.morrison/john/cygwin/update-defaults/defa ults.html (this should be added to the 'how to create a package' instructions, or something like?) http://homepage.ntlworld.com/j-n-s.morrison/john/cygwin/update-defaults/setu p.hint http://homepage.ntlworld.com/j-n-s.morrison/john/cygwin/update-defaults/md5s um Also, re-done base-files using this mechanism... http://homepage.ntlworld.com/j-n-s.morrison/john/cygwin/base-files/base-file s-1.2-1.tar.bz2 http://homepage.ntlworld.com/j-n-s.morrison/john/cygwin/base-files/setup.hin t http://homepage.ntlworld.com/j-n-s.morrison/john/cygwin/base-files/md5sum Christopher: is this OK? You don't need my permission. Just post to cygwin-apps and see what others think. Or, since you're the package maintainer and, I'm sure that you've tested this, feel free to just refresh your packages. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: FAO: cfg: defaults
[Redirecting to cygwin-apps] On Sat, Jan 04, 2003 at 03:17:40PM -0500, Christopher Faylor wrote: On Sat, Jan 04, 2003 at 04:50:41PM -, John Morrison wrote: From: Christopher Faylor On Mon, Dec 02, 2002 at 12:56:03PM -, Morrison, John wrote: You'd probably want something like: snip/ setup.hint: sdesc: Conditionally move default files to proper location category: _PostInstallLast requires: ash findutils fileutils sed sh-utils autodep: etc/defaults/.* incver_ifdep: yes This would run automatically whenever packages are downloaded and installed in one shot. It wouldn't run if someone downloads everything and then installs piecemeal, though. I think there are lots of things that don't work when cygwin is not installed via setup. I can't think of any other way... The script to move the files would be the only thing in the package and it would be a post-install script. Done :) Please find for you perusal and review... (long links, will wrap!) http://homepage.ntlworld.com/j-n-s.morrison/john/cygwin/update-defaults/upda te-defaults-1.0-.tar.bz2 http://homepage.ntlworld.com/j-n-s.morrison/john/cygwin/update-defaults/defa ults.html (this should be added to the 'how to create a package' instructions, or something like?) http://homepage.ntlworld.com/j-n-s.morrison/john/cygwin/update-defaults/setu p.hint http://homepage.ntlworld.com/j-n-s.morrison/john/cygwin/update-defaults/md5s um Also, re-done base-files using this mechanism... http://homepage.ntlworld.com/j-n-s.morrison/john/cygwin/base-files/base-file s-1.2-1.tar.bz2 http://homepage.ntlworld.com/j-n-s.morrison/john/cygwin/base-files/setup.hin t http://homepage.ntlworld.com/j-n-s.morrison/john/cygwin/base-files/md5sum Christopher: is this OK? You don't need my permission. Just post to cygwin-apps and see what others think. Or, since you're the package maintainer and, I'm sure that you've tested this, feel free to just refresh your packages. Actually, I do have one comment. If you are using incver_ifdep in setup.hint then you should name the package something like foo-01-1.tar.bz2. The 01 part gets updated every time there is a package which relies on it. If you use something like 1.2, I'm not sure exactly what will happen. It may just increment it to 1.3, 1.4, etc., but I don't know for sure. Also, how about posting the text bits to the mailing list rather than having us cut and paste a URL for perusal? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: FAO: cfg: defaults
John, At 08:50 2003-01-04, John Morrison wrote: ... Please find for you perusal and review... (long links, will wrap!) Why don't you enclose all URLs in email within angle brackets instead of forcing people to reintegrate the wrapped links? Even a short URL can fall on a line wrap boundary if embedded in other text. http://homepage.ntlworld.com/j-n-s.morrison/john/cygwin/update-defaults/update-defaults-1.0-.tar.bz2 http://homepage.ntlworld.com/j-n-s.morrison/john/cygwin/update-defaults/defaults.html (this should be added to the 'how to create a package' instructions, or something like?) http://homepage.ntlworld.com/j-n-s.morrison/john/cygwin/update-defaults/setup.hint http://homepage.ntlworld.com/j-n-s.morrison/john/cygwin/update-defaults/md5sum Also, re-done base-files using this mechanism... http://homepage.ntlworld.com/j-n-s.morrison/john/cygwin/base-files/base-files-1.2-1.tar.bz2 http://homepage.ntlworld.com/j-n-s.morrison/john/cygwin/base-files/setup.hint http://homepage.ntlworld.com/j-n-s.morrison/john/cygwin/base-files/md5sum Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: FAO: cfg: defaults
On Sat, Jan 04, 2003 at 04:24:53PM -0800, Randall R Schulz wrote: At 08:50 2003-01-04, John Morrison wrote: Please find for you perusal and review... (long links, will wrap!) Why don't you enclose all URLs in email within angle brackets instead of forcing people to reintegrate the wrapped links? Even a short URL can fall on a line wrap boundary if embedded in other text. I've noticed that people do this and I'm always curious as to why. Is there a mail reader convention that causes angle bracket wrapped URLs to be properly understood? I know that my mail reader doesn't understand them but... cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: FAO: cfg: defaults
On Sun, 2003-01-05 at 12:33, Christopher Faylor wrote: On Sat, Jan 04, 2003 at 04:24:53PM -0800, Randall R Schulz wrote: At 08:50 2003-01-04, John Morrison wrote: Please find for you perusal and review... (long links, will wrap!) Why don't you enclose all URLs in email within angle brackets instead of forcing people to reintegrate the wrapped links? Even a short URL can fall on a line wrap boundary if embedded in other text. I've noticed that people do this and I'm always curious as to why. Is there a mail reader convention that causes angle bracket wrapped URLs to be properly understood? I know that my mail reader doesn't understand them but... Yes, there is. Uhmm, I *think* it was Eudora years and years ago that did it first. Rob -- --- GPG key available at: http://users.bigpond.net.au/robertc/keys.txt. --- signature.asc Description: This is a digitally signed message part
Re: FAO: cfg: defaults
On Sat, Jan 04, 2003 at 05:58:10PM -0800, Randall R Schulz wrote: Chris, I think it's in one of the email RFCs. I remember tracking it down once during an (ill-considered) debate on one of the Bay Area Usenet groups. I should have made note of where I found it, but I didn't. I can find a variety of non-official mentions of this as a recommended convention using Google, but the relevant RFCs are numerous and voluminous. I'll try to find something definitive and authoritative and let you know. (It's one of those pet peeve / crusade things for me to get people to use these things, so the authority of the IETF is something good to have at hand.) Thanks. I'm glad I asked. I probably should have implemented something for my email reader a while ago. This might spur me on to do that. Hmm. I guess I'm getting off-topic now. *Slap* cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: FAO: cfg: defaults
Chris, I hope this isn't too far off-topic or excessive in its protractedness. If you'd like, I'll tease the cat a little and get some scratches on my arms. Anyway, I found this in RFC 1738, Uniform Resource Locators (URL) (http://www.ietf.org/rfc/rfc1738.txt, lines 1183 through 1225): -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- APPENDIX: Recommendations for URLs in Context URIs, including URLs, are intended to be transmitted through protocols which provide a context for their interpretation. In some cases, it will be necessary to distinguish URLs from other possible data structures in a syntactic structure. In this case, is recommended that URLs be preceeded with a prefix consisting of the characters URL:. For example, this prefix may be used to distinguish URLs from other kinds of URIs. In addition, there are many occasions when URLs are included in other kinds of text; examples include electronic mail, USENET news messages, or printed on paper. In such cases, it is convenient to have a separate syntactic wrapper that delimits the URL and separates it from the rest of the text, and in particular from punctuation marks that might be mistaken for part of the URL. For this purpose, is recommended that angle brackets ( and ), along with the prefix URL:, be used to delimit the boundaries of the URL. This wrapper does not form part of the URL and should not be used in contexts in which delimiters are already specified. In the case where a fragment/anchor identifier is associated with a URL (following a #), the identifier would be placed within the brackets as well. In some cases, extra whitespace (spaces, linebreaks, tabs, etc.) may need to be added to break long URLs across lines. The whitespace should be ignored when extracting the URL. No whitespace should be introduced after a hyphen (-) character. Because some typesetters and printers may (erroneously) introduce a hyphen at the end of line when breaking a line, the interpreter of a URL containing a line break immediately after a hyphen should ignore all unencoded whitespace around the line break, and should be aware that the hyphen may or may not actually be part of the URL. Examples: Yes, Jim, I found it under URL:ftp://info.cern.ch/pub/www/doc; type=d but you can probably pick it up from URL:ftp://ds.in ternic.net/rfc. Note the warning in URL:http://ds.internic. net/instructions/overview.html#WARNING. -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- I guess this passage, appearing as it does in an appendix with the title Recommendations ..., does not have the force of a standard per se, but it's good enough for me. I notice as I peruse the RFCs that this recommendation (including URL: part) is widely used in the plain-text RFCs. RFC 2369 The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields is also somewhat relevant and indicates that for its purposes within headers, the angle brackets are in fact mandatory and specified within the RFC proper. Randall Schulz At 18:08 2003-01-04, Christopher Faylor wrote: On Sat, Jan 04, 2003 at 05:58:10PM -0800, Randall R Schulz wrote: Chris, I think it's in one of the email RFCs. I remember tracking it down once during an (ill-considered) debate on one of the Bay Area Usenet groups. I should have made note of where I found it, but I didn't. I can find a variety of non-official mentions of this as a recommended convention using Google, but the relevant RFCs are numerous and voluminous. I'll try to find something definitive and authoritative and let you know. (It's one of those pet peeve / crusade things for me to get people to use these things, so the authority of the IETF is something good to have at hand.) Thanks. I'm glad I asked. I probably should have implemented something for my email reader a while ago. This might spur me on to do that. Hmm. I guess I'm getting off-topic now. *Slap* cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
