[ITP] wtf
As per John Morrison's suggestion, I would like to contribute and maintain wtf (http://cronus.comp.utas.edu.au/~thsutton/computing/wtf.html). wtf(6) is a utility provided by some UNIX and UNIX-like systems including Slackware Linux and NetBSD. It translates acronyms and filename suffixes by looking up the definition of a term in various databases. I've added the OLOCA to the database directory (named %OLOCA to place it first in search order). There's also a perl script that can update that file from the web version of the OLOCA (also requires wget), but since this rule is totally optional (and won't be invoked in the default build), I didn't put perl and wget as prerequisites for building wtf. This is mentioned in wtf.README as well. http://cs.nyu.edu/~pechtcha/cygwin/wtf/wtf-0.0.3-1.tar.bz2 http://cs.nyu.edu/~pechtcha/cygwin/wtf/wtf-0.0.3-1-src.tar.bz2 http://cs.nyu.edu/~pechtcha/cygwin/wtf/setup.hint (also inline below) sdesc: "translates acronyms and filename suffixes for you" ldesc: "wtf translates acronyms and filename suffixes for you. The wtf program looks-up the definition of a term. It supports a number of definition sources. In this version they are an acronyms database and qa filename suffixes database." requires: cygwin category: Text Doc Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton
Re: [ITP] wtf
On Mon, Jul 28, 2003 at 08:17:11PM -0400, Igor Pechtchanski wrote: > As per John Morrison's suggestion, I would like to contribute and maintain > wtf (http://cronus.comp.utas.edu.au/~thsutton/computing/wtf.html). > > wtf(6) is a utility provided by some UNIX and UNIX-like systems including > Slackware Linux and NetBSD. It translates acronyms and filename suffixes > by looking up the definition of a term in various databases. > > I've added the OLOCA to the database directory (named %OLOCA to place it > first in search order). There's also a perl script that can update that > file from the web version of the OLOCA (also requires wget), but since > this rule is totally optional (and won't be invoked in the default build), > I didn't put perl and wget as prerequisites for building wtf. This is > mentioned in wtf.README as well. > > http://cs.nyu.edu/~pechtcha/cygwin/wtf/wtf-0.0.3-1.tar.bz2 > http://cs.nyu.edu/~pechtcha/cygwin/wtf/wtf-0.0.3-1-src.tar.bz2 > http://cs.nyu.edu/~pechtcha/cygwin/wtf/setup.hint (also inline below) > > sdesc: "translates acronyms and filename suffixes for you" > ldesc: "wtf translates acronyms and filename suffixes for you. > > The wtf program looks-up the definition of a term. It supports a > number of definition sources. In this version they are an acronyms > database and qa filename suffixes database." > requires: cygwin > category: Text Doc This has my vote. -- +---+ | Marcel Telka e-mail: [EMAIL PROTECTED] | |homepage: http://telka.sk/ | |jabber: [EMAIL PROTECTED] | +---+
RE: [ITP] wtf
Igor Pechtchanski wrote: > As per John Morrison's suggestion, I would like to contribute and > maintain wtf > (http://cronus.comp.utas.edu.au/~thsutton/computing/wtf.html). > > wtf(6) is a utility provided by some UNIX and UNIX-like systems > including Slackware Linux and NetBSD. It translates acronyms and > filename suffixes by looking up the definition of a term in various > databases. > > I've added the OLOCA to the database directory (named %OLOCA to place > it first in search order). There's also a perl script that can > update that file from the web version of the OLOCA (also requires > wget), but since this rule is totally optional (and won't be invoked > in the default build), I didn't put perl and wget as prerequisites > for building wtf. This is mentioned in wtf.README as well. > > http://cs.nyu.edu/~pechtcha/cygwin/wtf/wtf-0.0.3-1.tar.bz2 > http://cs.nyu.edu/~pechtcha/cygwin/wtf/wtf-0.0.3-1-src.tar.bz2 > http://cs.nyu.edu/~pechtcha/cygwin/wtf/setup.hint (also inline below) > > sdesc: "translates acronyms and filename suffixes for you" > ldesc: "wtf translates acronyms and filename suffixes for you. > > The wtf program looks-up the definition of a term. It supports a > number of definition sources. In this version they are an acronyms > database and qa filename suffixes database." > requires: cygwin > category: Text Doc > > Igor Has my vote :) J. === Information in this email and any attachments are confidential, and may not be copied or used by anyone other than the addressee, nor disclosed to any third party without our permission. There is no intention to create any legally binding contract or other commitment through the use of this email. Experian Limited (registration number 653331). Registered office: Talbot House, Talbot Street, Nottingham NG1 5HF
Re: [ITP] wtf
Has my vote, Just a small note, though: most of the OLOCA acronyms are a lot more verbose than their wtf counterparts, and some of them are duplicates. would it be possible to adapt your Perl script to weed out the (exact) duplicates? JAT (*) rlc (*) JAT: Just A Thought - neither in wtf nor the OLOCA I'm afraid.. On Mon, Jul 28, 2003 at 08:17:11PM -0400, Igor Pechtchanski wrote: > As per John Morrison's suggestion, I would like to contribute and maintain > wtf (http://cronus.comp.utas.edu.au/~thsutton/computing/wtf.html). > > wtf(6) is a utility provided by some UNIX and UNIX-like systems including > Slackware Linux and NetBSD. It translates acronyms and filename suffixes > by looking up the definition of a term in various databases. > > I've added the OLOCA to the database directory (named %OLOCA to place it > first in search order). There's also a perl script that can update that > file from the web version of the OLOCA (also requires wget), but since > this rule is totally optional (and won't be invoked in the default build), > I didn't put perl and wget as prerequisites for building wtf. This is > mentioned in wtf.README as well. > > http://cs.nyu.edu/~pechtcha/cygwin/wtf/wtf-0.0.3-1.tar.bz2 > http://cs.nyu.edu/~pechtcha/cygwin/wtf/wtf-0.0.3-1-src.tar.bz2 > http://cs.nyu.edu/~pechtcha/cygwin/wtf/setup.hint (also inline below) > > sdesc: "translates acronyms and filename suffixes for you" > ldesc: "wtf translates acronyms and filename suffixes for you. > > The wtf program looks-up the definition of a term. It supports a > number of definition sources. In this version they are an acronyms > database and qa filename suffixes database." > requires: cygwin > category: Text Doc > > Igor > -- > http://cs.nyu.edu/~pechtcha/ > |\ _,,,---,,_[EMAIL PROTECTED] > ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] > |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. > '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! > > "I have since come to realize that being between your mentor and his route > to the bathroom is a major career booster." -- Patrick Naughton > > --
Re: [ITP] wtf
Great, that makes 3 votes. Now all I have to do is get someone to review the packaging (nudge, nudge, wink, wink). I don't see a particular value in weeding out duplicates, as all variants will be displayed, so no information is lost. However, I'll see if I could "hide" the original acronyms... Anyway, I'll work on the perl script and on getting the acronym list up to date (there have been some changes in the OLOCA) in the next few days, and will release a new iteration of the package then. The packaging won't change, so the current one can be reviewed, but please don't upload it until I post the new one (I'll notify the list, obviously). Thanks, Igor On Mon, 4 Aug 2003, Ronald Landheer-Cieslak wrote: > Has my vote, > > Just a small note, though: most of the OLOCA acronyms are a lot more verbose > than their wtf counterparts, and some of them are duplicates. would it be > possible to adapt your Perl script to weed out the (exact) duplicates? > > JAT (*) > > rlc > > (*) JAT: Just A Thought - neither in wtf nor the OLOCA I'm afraid.. > > On Mon, Jul 28, 2003 at 08:17:11PM -0400, Igor Pechtchanski wrote: > > As per John Morrison's suggestion, I would like to contribute and maintain > > wtf (http://cronus.comp.utas.edu.au/~thsutton/computing/wtf.html). > > > > wtf(6) is a utility provided by some UNIX and UNIX-like systems including > > Slackware Linux and NetBSD. It translates acronyms and filename suffixes > > by looking up the definition of a term in various databases. > > > > I've added the OLOCA to the database directory (named %OLOCA to place it > > first in search order). There's also a perl script that can update that > > file from the web version of the OLOCA (also requires wget), but since > > this rule is totally optional (and won't be invoked in the default build), > > I didn't put perl and wget as prerequisites for building wtf. This is > > mentioned in wtf.README as well. > > > > http://cs.nyu.edu/~pechtcha/cygwin/wtf/wtf-0.0.3-1.tar.bz2 > > http://cs.nyu.edu/~pechtcha/cygwin/wtf/wtf-0.0.3-1-src.tar.bz2 > > http://cs.nyu.edu/~pechtcha/cygwin/wtf/setup.hint (also inline below) > > > > sdesc: "translates acronyms and filename suffixes for you" > > ldesc: "wtf translates acronyms and filename suffixes for you. > > > > The wtf program looks-up the definition of a term. It supports a > > number of definition sources. In this version they are an acronyms > > database and qa filename suffixes database." > > requires: cygwin > > category: Text Doc > > > > Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton
Re: [ITP] wtf
On Mon, Aug 04, 2003 at 08:56:57AM -0400, Igor Pechtchanski wrote: > Great, that makes 3 votes. Now all I have to do is get someone to review > the packaging (nudge, nudge, wink, wink). FWIW, I've installed the binary - it seems to be working nicely. I've tried bowth wtf and wtfindex. I've also recompiled the source to see if I can - no problems.. > I don't see a particular value in weeding out duplicates, as all variants > will be displayed, so no information is lost. Actually, they only get displayed if they're in different files - bug? > However, I'll see if I could "hide" the original acronyms... The thing that got me to ask was this: $ wtf iirc iirc: If I Recall Correctly iirc: if I recall correctly and personally, I think this may come off as odd: $ wtf iwfm iwfm: It Works For Me. Also WFM. Corinna, you want credit for this one? someone not familiar with the web version of the OLOCA might frown at this.. I don't really mind, though.. However, there are some things not quite in accordance with the wtf way of doing things in the OLOCA: $ wtf Cygwin Cygwin: Multiple variants have been suggested, take your pick: Coolness You Get Where Initially None (mine) Can You Guess What's Implemented Next (mine) Cramming Your Gut With Indispensable Necessities (Gary R. Van Sickle) Cygwin: Your Greatest Winner In Necessities (Ronald Landheer-Cieslak) Can't You Get With It, Ninnies? (Christopher Faylor) IMHO, this should be $ wtf Cygwin Cygwin: Coolness You Get Where Initially None (mine) Cygwin: Can You Guess What's Implemented Next (mine) Cygwin: Cramming Your Gut With Indispensable Necessities (Gary R. Van Sickle) Cygwin: Cygwin: Your Greatest Winner In Necessities (Ronald Landheer-Cieslak) Cygwin: Can't You Get With It, Ninnies? (Christopher Faylor) but I don't see how to do that at the moment - at least not without either patching wtf so it takes multiple entries for the same acronym in a single file into account, or making several files for the various duplicates.. Hmm.. this looks like a PTC situation.. Anyways, this doesn't alter my vote in any way :) Perhaps, if I have the time @ home, I'll work out a patch to handle different meanings for the same acronym "correctly" .. perhaps .. ah, for time 'tis such a precious gift wasting it's a heinous crime for it should be spent in thrift rlc > Anyway, I'll work on the perl script and on getting the acronym list up to > date (there have been some changes in the OLOCA) in the next few days, and > will release a new iteration of the package then. The packaging won't > change, so the current one can be reviewed, but please don't upload it > until I post the new one (I'll notify the list, obviously). Thanks, > Igor > > On Mon, 4 Aug 2003, Ronald Landheer-Cieslak wrote: > > > Has my vote, > > > > Just a small note, though: most of the OLOCA acronyms are a lot more verbose > > than their wtf counterparts, and some of them are duplicates. would it be > > possible to adapt your Perl script to weed out the (exact) duplicates? > > > > JAT (*) > > > > rlc > > > > (*) JAT: Just A Thought - neither in wtf nor the OLOCA I'm afraid.. > > > > On Mon, Jul 28, 2003 at 08:17:11PM -0400, Igor Pechtchanski wrote: > > > As per John Morrison's suggestion, I would like to contribute and maintain > > > wtf (http://cronus.comp.utas.edu.au/~thsutton/computing/wtf.html). > > > > > > wtf(6) is a utility provided by some UNIX and UNIX-like systems including > > > Slackware Linux and NetBSD. It translates acronyms and filename suffixes > > > by looking up the definition of a term in various databases. > > > > > > I've added the OLOCA to the database directory (named %OLOCA to place it > > > first in search order). There's also a perl script that can update that > > > file from the web version of the OLOCA (also requires wget), but since > > > this rule is totally optional (and won't be invoked in the default build), > > > I didn't put perl and wget as prerequisites for building wtf. This is > > > mentioned in wtf.README as well. > > > > > > http://cs.nyu.edu/~pechtcha/cygwin/wtf/wtf-0.0.3-1.tar.bz2 > > > http://cs.nyu.edu/~pechtcha/cygwin/wtf/wtf-0.0.3-1-src.tar.bz2 > > > http://cs.nyu.edu/~pechtcha/cygwin/wtf/setup.hint (also inline below) > > > > > > sdesc: "translates acronyms and filename suffixes for you" > > > ldesc: "wtf translates acronyms and filename suffixes for you. > > > > > > The wtf program looks-up the definition of a term. It supports a > > > number of definition sources. In this version they are an acronyms > > > database and qa filename suffixes database." > > > requires: cygwin > > > category: Text Doc > > > > > > Igor > > -- > http://cs.nyu.edu/~pechtcha/ > |\ _,,,---,,_ [EMAIL PROTECTED] > ZZZzz /,`.-'`'-. ;-;;,_ [EMAIL PROTECTED] > |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. > '---''(_/--' `-'\_) fL a.
Re: [ITP] wtf
Ronald, Replies inline below. On Mon, 4 Aug 2003, Ronald Landheer-Cieslak wrote: > On Mon, Aug 04, 2003 at 08:56:57AM -0400, Igor Pechtchanski wrote: > > Great, that makes 3 votes. Now all I have to do is get someone to review > > the packaging (nudge, nudge, wink, wink). > FWIW, I've installed the binary - it seems to be working nicely. I've tried > bowth wtf and wtfindex. > I've also recompiled the source to see if I can - no problems.. Great. Is the packaging structure ok? Should I move the manpages to /usr/share/man while I'm at it? > > I don't see a particular value in weeding out duplicates, as all variants > > will be displayed, so no information is lost. > Actually, they only get displayed if they're in different files - bug? Umm, no, a feature. Basically, the files are indexed by the acronym, so duplicate entries in the same file get lost. Since different files use different indices... In short, this is unlikely to change any time soon. > > However, I'll see if I could "hide" the original acronyms... > The thing that got me to ask was this: > $ wtf iirc > iirc: If I Recall Correctly > iirc: if I recall correctly Ah, yes, I see. Well, I'll try to work on this in the next release, maybe. Otherwise, this is not too harmful. > and personally, I think this may come off as odd: > $ wtf iwfm > iwfm: It Works For Me. Also WFM. Corinna, you want credit for this one? > > someone not familiar with the web version of the OLOCA might frown at this.. > I don't really mind, though.. Agreed. However, in the interests of expediency, I'm going to keep the automatic transformation of the web version for now. > However, there are some things not quite in accordance with the wtf way of > doing things in the OLOCA: > > $ wtf Cygwin > Cygwin: Multiple variants have been suggested, take your pick: Coolness You Get > Where Initially None (mine) Can You Guess What's Implemented Next (mine) Cramming > Your Gut With Indispensable Necessities (Gary R. Van Sickle) Cygwin: Your Greatest > Winner In Necessities (Ronald Landheer-Cieslak) Can't You Get With It, Ninnies? > (Christopher Faylor) > > IMHO, this should be > $ wtf Cygwin > Cygwin: Coolness You Get Where Initially None (mine) > Cygwin: Can You Guess What's Implemented Next (mine) > Cygwin: Cramming Your Gut With Indispensable Necessities (Gary R. Van Sickle) > Cygwin: Cygwin: Your Greatest Winner In Necessities (Ronald Landheer-Cieslak) > Cygwin: Can't You Get With It, Ninnies? (Christopher Faylor) How about $ wtf Cygwin Cygwin: Multiple variants have been suggested, take your pick: - Coolness You Get Where Initially None (mine) - Can You Guess What's Implemented Next (mine) - Cramming Your Gut With Indispensable Necessities (Gary R. Van Sickle) - Cygwin: Your Greatest Winner In Necessities (Ronald Landheer-Cieslak) - Can't You Get With It, Ninnies? (Christopher Faylor) ? ;-) > but I don't see how to do that at the moment - at least not without either > patching wtf so it takes multiple entries for the same acronym in a single > file into account, or making several files for the various duplicates.. > > Hmm.. this looks like a PTC situation.. Well, I've done this by reformatting the list entries for 80-column screen. Those with larger ones can always reformat it (see the README). I'll see about getting some way of encoding newlines into the descriptions and passing the patch to the upstream maintainer. > Anyways, this doesn't alter my vote in any way :) > > Perhaps, if I have the time @ home, I'll work out a patch to handle different > meanings for the same acronym "correctly" .. perhaps .. > > ah, for time > 'tis such a precious gift > wasting it's a heinous crime > for it should be spent in thrift > > > rlc Ok. I've posted a new version of the package (at the URLs quoted below). It contains the updates from the web version of the OLOCA (including "JAT" and "JTYMLTK"), as well as better formatting for the Cygwin acronym. This one is actually ready to be uploaded. Thanks for the reviews and the votes. Igor > > Anyway, I'll work on the perl script and on getting the acronym list up to > > date (there have been some changes in the OLOCA) in the next few days, and > > will release a new iteration of the package then. The packaging won't > > change, so the current one can be reviewed, but please don't upload it > > until I post the new one (I'll notify the list, obviously). Thanks, > > Igor > > > > On Mon, 4 Aug 2003, Ronald Landheer-Cieslak wrote: > > > > > Has my vote, > > > > > > Just a small note, though: most of the OLOCA acronyms are a lot more verbose > > > than their wtf counterparts, and some of them are duplicates. would it be > > > possible to adapt your Perl script to weed out the (exact) duplicates? > > > > > > JAT (*) > > > > > > rlc > > > > > > (*) JAT: Just A Thought - neither in wtf nor the OLOCA I'm afraid.. > > > > > > On Mon, Jul 28, 2003 at 08:17:11PM -0400, Igor Pechtc
Re: [ITP] wtf
On Mon, Aug 04, 2003 at 10:21:35PM -0400, Igor Pechtchanski wrote: > On Mon, 4 Aug 2003, Ronald Landheer-Cieslak wrote: > > On Mon, Aug 04, 2003 at 08:56:57AM -0400, Igor Pechtchanski wrote: > > > Great, that makes 3 votes. Now all I have to do is get someone to review > > > the packaging (nudge, nudge, wink, wink). > > FWIW, I've installed the binary - it seems to be working nicely. I've tried > > bowth wtf and wtfindex. > > I've also recompiled the source to see if I can - no problems.. > Great. Is the packaging structure ok? Should I move the manpages to > /usr/share/man while I'm at it? IMHO, it's a good idea on the way to normalizing the Cygwin tree, but I'm not picky about it (seeing as pcre isn't normalized in this way yet) Other than that (and including that too) the structure looks OK to me. I've just read the README as well - looks OK too (though I wouldn't have added the and would have added the .exe suffix for the diff. executables, but that's just me..) > > > I don't see a particular value in weeding out duplicates, as all variants > > > will be displayed, so no information is lost. > > Actually, they only get displayed if they're in different files - bug? > Umm, no, a feature. Basically, the files are indexed by the acronym, so > duplicate entries in the same file get lost. Since different files use > different indices... In short, this is unlikely to change any time soon. The difference between a bug and a feature is often in the eye of the beholder ;) > > > However, I'll see if I could "hide" the original acronyms... > > The thing that got me to ask was this: > > $ wtf iirc > > iirc: If I Recall Correctly > > iirc: if I recall correctly > Ah, yes, I see. Well, I'll try to work on this in the next release, > maybe. Otherwise, this is not too harmful. I agree :) > > and personally, I think this may come off as odd: > > $ wtf iwfm > > iwfm: It Works For Me. Also WFM. Corinna, you want credit for this one? > > > > someone not familiar with the web version of the OLOCA might frown at this.. > > I don't really mind, though.. > Agreed. However, in the interests of expediency, I'm going to keep the > automatic transformation of the web version for now. > > > However, there are some things not quite in accordance with the wtf way of > > doing things in the OLOCA: > > > > $ wtf Cygwin > > Cygwin: Multiple variants have been suggested, take your pick: Coolness You Get > > Where Initially None (mine) Can You Guess What's Implemented Next (mine) Cramming > > Your Gut With Indispensable Necessities (Gary R. Van Sickle) Cygwin: Your Greatest > > Winner In Necessities (Ronald Landheer-Cieslak) Can't You Get With It, Ninnies? > > (Christopher Faylor) > > > > IMHO, this should be > > $ wtf Cygwin > > Cygwin: Coolness You Get Where Initially None (mine) > > Cygwin: Can You Guess What's Implemented Next (mine) > > Cygwin: Cramming Your Gut With Indispensable Necessities (Gary R. Van Sickle) > > Cygwin: Cygwin: Your Greatest Winner In Necessities (Ronald Landheer-Cieslak) > > Cygwin: Can't You Get With It, Ninnies? (Christopher Faylor) > > How about > $ wtf Cygwin > Cygwin: Multiple variants have been suggested, take your pick: > - Coolness You Get Where Initially None (mine) > - Can You Guess What's Implemented Next (mine) > - Cramming Your Gut With Indispensable Necessities (Gary R. Van Sickle) > - Cygwin: Your Greatest Winner In Necessities (Ronald Landheer-Cieslak) > - Can't You Get With It, Ninnies? (Christopher Faylor) > ? ;-) > > > but I don't see how to do that at the moment - at least not without either > > patching wtf so it takes multiple entries for the same acronym in a single > > file into account, or making several files for the various duplicates.. > > > > Hmm.. this looks like a PTC situation.. > > Well, I've done this by reformatting the list entries for 80-column > screen. Those with larger ones can always reformat it (see the README). > I'll see about getting some way of encoding newlines into the descriptions > and passing the patch to the upstream maintainer. Actually, the part I tried is a way of encoding newlines into the descriptions, which is why I though it to be a PTC situation :) > Ok. I've posted a new version of the package (at the URLs quoted below). > It contains the updates from the web version of the OLOCA (including "JAT" > and "JTYMLTK"), as well as better formatting for the Cygwin acronym. This > one is actually ready to be uploaded. Thanks for the reviews and the > votes. You're quite welcome :) Thanks for the packaging :) rlc
Re: [ITP] wtf
Igor Pechtchanski wrote: Great. Is the packaging structure ok? Should I move the manpages to /usr/share/man while I'm at it? I think so. While recompiling all of my packages (again) for 1.5.1, I moved all documentation into /usr/share/* since that seemed to (a) make sense, (b) have some support on the list, and (c) NOT have any strident opposition. There may be some short-term issues with _update-info-dir/INFOPATH/MANPATH, but those can be fixed asynchronously, and do not appear to be truly problematic or otherwise unsolvable. -- Chuck
Re: [ITP] wtf
On Tue, 5 Aug 2003 07:58:36 -0400 (EDT), "Igor Pechtchanski" <[EMAIL PROTECTED]> said: > Ah, I thought so. Ok, then, how about I leave them in /usr/man for now, > and move them to /usr/share/man when I recompile the package against > 1.5.*? Sounds like a plan. -- Charles Wilson cygwin at removespam cwilson dot fastmail dot fm
Re: [ITP] wtf
On Tue, 5 Aug 2003, Charles Wilson wrote: > Igor Pechtchanski wrote: > > > Great. Is the packaging structure ok? Should I move the manpages to > > /usr/share/man while I'm at it? > > I think so. While recompiling all of my packages (again) for 1.5.1, I > moved all documentation into /usr/share/* since that seemed to (a) make > sense, (b) have some support on the list, and (c) NOT have any strident > opposition. > > There may be some short-term issues with > _update-info-dir/INFOPATH/MANPATH, but those can be fixed > asynchronously, and do not appear to be truly problematic or otherwise > unsolvable. > > Chuck Ah, I thought so. Ok, then, how about I leave them in /usr/man for now, and move them to /usr/share/man when I recompile the package against 1.5.*? Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton
Re: [ITP] wtf
Igor Pechtchanski <[EMAIL PROTECTED]> wrote:
> Ronald,
>
> Replies inline below.
>
> On Mon, 4 Aug 2003, Ronald Landheer-Cieslak wrote:
>
> > On Mon, Aug 04, 2003 at 08:56:57AM -0400, Igor Pechtchanski wrote:
> > > Great, that makes 3 votes. Now all I have to do is get someone to review
> > > the packaging (nudge, nudge, wink, wink).
> > FWIW, I've installed the binary - it seems to be working nicely. I've tried
> > bowth wtf and wtfindex.
> > I've also recompiled the source to see if I can - no problems..
>
> Great. Is the packaging structure ok? Should I move the manpages to
> /usr/share/man while I'm at it?
I think /usr/{doc,man} is OK for now (as you've said in a follow-up). When you
update for 1.5 ...
> [...]
> Ok. I've posted a new version of the package (at the URLs quoted below).
> It contains the updates from the web version of the OLOCA (including "JAT"
> and "JTYMLTK"), as well as better formatting for the Cygwin acronym. This
> one is actually ready to be uploaded. Thanks for the reviews and the
> votes.
> Igor
I've uploaded wtf. Please send an announcement in a couple of hours.
Thanks,
-- Elfyn
PS- Sorry to you and everyone else who's been waiting for this stuff to get done.
I've had outgoing mail problems which were only (properly) fixed this morning.
I'm going to spend my Sunday, staring at my screen, catching up. ":-)"
