Re: Units
Last time I simply removed the `test' marker. This time I'll ask. John, are you sure that it should become a `test' version? Please see setup.html. It explicitly requires this for new packages. Rob
Re: Units
Ok, I bit. Step 5: 5. Create setup.hint file following the documentation on this web page. For new packages the first upload MUST be tagged as experimental. Once the package has no major bug reports from the users, then a current package may be introduced Rob
Re: Units
On Thu, Dec 20, 2001 at 08:53:30PM +1100, Robert Collins wrote: Ok, I bit. Step 5: 5. Create setup.hint file following the documentation on this web page. For new packages the first upload MUST be tagged as experimental. Once the package has no major bug reports from the users, then a current package may be introduced I hate that. Quote from a few lines above the `setup.hint' section: Test versions are specified via the setup.hint file as described below. It is not required that your package have a test version. Use of a test version of a package is at the discretion of the package maintainer. And how long does it take to wait for major bug reports from the users? 1 day? A week? A month? Not amused, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] Red Hat, Inc.
RE: bash completion (was: RE: Units)
I found a problem with the bash_completion as stands... I have a path ~/Applications/Apache Group/ with no other directory in Applications starting with 'A'. When I cd ~/Applications/A[tab] it doesn't autocomplete. When I look through the shell script I can see... snippit # Turn on extended globbing and programmable completion shopt -s extglob progcomp # A lot of the following one-liners were taken directly from the # completion examples provided with the bash 2.04 source distribution # Make directory commands see only directories complete -d cd mkdir rmdir pushd /snippit removing 'cd' from the complete -d doesn't fix this. I'm CC'ing the original author (Ian Caliban). If cygwin folks want to take it and take a look I still recommend doing so (all the other things I've tried work very nicely), as for putting it in the distro I'd prefer to find out if this is expected behaviour or not. Sorry to have caused so much hassle just to retract it :( 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: bash completion (was: RE: Units)
=== - Original Message - From: Morrison, John [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, December 20, 2001 10:02 PM Subject: RE: bash completion (was: RE: Units) I found a problem with the bash_completion as stands... ... Sorry to have caused so much hassle just to retract it :( I wouldn't worry - this is the whole point of having new packages start out as 'experimental'. It allows some breathing room. Rob
Re: bash completion (was: RE: Units)
On Thu, Dec 20, 2001 at 11:02:07AM -, Morrison, John wrote: I found a problem with the bash_completion as stands... I have a path ~/Applications/Apache Group/ with no other directory in Applications starting with 'A'. When I cd ~/Applications/A[tab] it doesn't autocomplete. That's actually weird. I'm using default completion in bash and I don't see a problem with `cd /cygdrive/c/DocTAB'. It completes correctly to `cd /cygdrive/c/Documents\ and\ Settings/'. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] Red Hat, Inc.
RE: bash completion (was: RE: Units)
-Original Message- From: Corinna Vinschen [mailto:[EMAIL PROTECTED]] Sent: Thursday, 20 December 2001 11:22 am To: '[EMAIL PROTECTED]' Subject: Re: bash completion (was: RE: Units) On Thu, Dec 20, 2001 at 11:02:07AM -, Morrison, John wrote: I found a problem with the bash_completion as stands... I have a path ~/Applications/Apache Group/ with no other directory in Applications starting with 'A'. When I cd ~/Applications/A[tab] it doesn't autocomplete. That's actually weird. I'm using default completion in bash and I don't see a problem with `cd /cygdrive/c/DocTAB'. It completes correctly to `cd /cygdrive/c/Documents\ and\ Settings/'. Yeah - that's what I used to get too - so I'm assuming it's something to do with this file... 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: Units
On Thu, Dec 13, 2001 at 03:40:35PM -, Morrison, John wrote: Hi, I've packaged up the latest version of units. I've just uploaded it to sourceware. You might consider to send a message to [EMAIL PROTECTED] in a few hours. Please keep the format as you will find it in the cygwin-announce mailing list archive. The announcement will automatically be propagated to the cygwin mailing list as soon as it has been approved so you don't need to send a second announcement to the base list. Thanks for the new package, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] Red Hat, Inc.
RE: Units
Thanks. Will do. btw, since you prob a *lot* more about bash than I do (since you're the maintainer for cygwin ;) have you any idea's why that's scripts messing cd's auto completion up? J. -Original Message- From: Corinna Vinschen [mailto:[EMAIL PROTECTED]] Sent: Thursday, 20 December 2001 11:29 am To: Morrison, John Cc: '[EMAIL PROTECTED]' Subject: Re: Units On Thu, Dec 13, 2001 at 03:40:35PM -, Morrison, John wrote: Hi, I've packaged up the latest version of units. I've just uploaded it to sourceware. You might consider to send a message to [EMAIL PROTECTED] in a few hours. Please keep the format as you will find it in the cygwin-announce mailing list archive. The announcement will automatically be propagated to the cygwin mailing list as soon as it has been approved so you don't need to send a second announcement to the base list. Thanks for the new package, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:[EMAIL PROTECTED] Red Hat, Inc. === 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: bash completion (was: RE: Units)
=== - Original Message - From: Morrison, John [EMAIL PROTECTED] To: 'Robert Collins' [EMAIL PROTECTED]; Morrison, John [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, December 20, 2001 10:50 PM Subject: RE: bash completion (was: RE: Units) Question: does experimental == test? If it does then we shouldn't refer to things as experimental but as being 'in test'. If not then should the test: line in setup.hint be changed to experimental: ? I know it's more typing but... True. Rob
which which
If you'll pardon the pun, which version of which are we running? The GNU version is currently 2.13 and I just wondered if folks would like and update...? (it compiles OOTB) 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: which which
=== - Original Message - From: Morrison, John [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, December 20, 2001 11:01 PM Subject: which which If you'll pardon the pun, which version of which are we running? The GNU version is currently 2.13 and I just wondered if folks would like and update...? (it compiles OOTB) I'm sure you could have answered the version question yourself: $ cygcheck -c which Cygwin Package Information Package Version which 1.5-1 And yes, IMO an update would be a Good Thing. Rob
RE: which which
I wasn't sure that: 1) we were using the GNU which (which --version doesn't work) and 2) by offering to update the package I wouldn't be offending the current(?) maintainer. J. BTW - It wasn't 1.5 in particular I wanted to know but whether it was the GNU which we were using. Which's are confusing :-) I'm sure you could have answered the version question yourself: $ cygcheck -c which Cygwin Package Information Package Version which 1.5-1 And yes, IMO an update would be a Good Thing. Rob swear/ done it *AGAIN*. Must remember - always reply-to-all! Sorry Robert. === 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: which which
Ah, well I've no idea about how GNU our version is. :}. Rob === - Original Message - From: Morrison, John [EMAIL PROTECTED] To: 'Robert Collins' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, December 20, 2001 11:23 PM Subject: RE: which which I wasn't sure that: 1) we were using the GNU which (which --version doesn't work) and 2) by offering to update the package I wouldn't be offending the current(?) maintainer. J. BTW - It wasn't 1.5 in particular I wanted to know but whether it was the GNU which we were using. Which's are confusing :-) I'm sure you could have answered the version question yourself: $ cygcheck -c which Cygwin Package Information Package Version which 1.5-1 And yes, IMO an update would be a Good Thing. Rob swear/ done it *AGAIN*. Must remember - always reply-to-all! Sorry Robert. === 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: Units
Corinna Vinschen wrote: On Thu, Dec 20, 2001 at 08:53:30PM +1100, Robert Collins wrote: Ok, I bit. Step 5: 5. Create setup.hint file following the documentation on this web page. For new packages the first upload MUST be tagged as experimental. Once the package has no major bug reports from the users, then a current package may be introduced I hate that. Quote from a few lines above the `setup.hint' section: Test versions are specified via the setup.hint file as described below. It is not required that your package have a test version. Use of a test version of a package is at the discretion of the package maintainer. And how long does it take to wait for major bug reports from the users? 1 day? A week? A month? Not amused, Corinna Nor, am I amused. If it must be tagged I'd rather see the tag NEW instead, unless the maintainer believes that it's actually an experimental version. Earnie. _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Re: Units
On Thu, Dec 20, 2001 at 11:39:13AM -, Morrison, John wrote: Thanks. Will do. btw, since you prob a *lot* more about bash than I do (since you're the maintainer for cygwin ;) have you any idea's why that's scripts messing cd's auto completion up? Prepared for disappointment? Ok, then, here we go: I'm using tcsh all the time, except I have to test something in or with bash. I'm not a bash expert, I'm justy maintaining it because somebody has to do it(tm). Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] Red Hat, Inc.
Re: which which
On Thu, Dec 20, 2001 at 11:23:38PM +1100, Robert Collins wrote: Ah, well I've no idea about how GNU our version is. :}. I contributed my own small version of which (which is version 1.5). If you want to maintain which in future, feel free to contribute the GNU version instead. I have actually no problems stepping back. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] Red Hat, Inc.
Re: which which
- Original Message - From: Corinna Vinschen [EMAIL PROTECTED] I contributed my own small version of which (which is version 1.5). If you want to maintain which in future, feel free to contribute the GNU version instead. I have actually no problems stepping back. I'm happy with either your version or the GNU version. I'd say it's up to you and John. Rob
RE: Units
Oh well - never mind :) I CC'd the original author, hopefully either he (or somebody on this list...? :) can fix it *GRIN*. J. -Original Message- From: Corinna Vinschen [mailto:[EMAIL PROTECTED]] Sent: Thursday, 20 December 2001 12:45 pm To: '[EMAIL PROTECTED]' Subject: Re: Units On Thu, Dec 20, 2001 at 11:39:13AM -, Morrison, John wrote: Thanks. Will do. btw, since you prob a *lot* more about bash than I do (since you're the maintainer for cygwin ;) have you any idea's why that's scripts messing cd's auto completion up? Prepared for disappointment? Ok, then, here we go: I'm using tcsh all the time, except I have to test something in or with bash. I'm not a bash expert, I'm justy maintaining it because somebody has to do it(tm). Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:[EMAIL PROTECTED] Red Hat, Inc. === 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: which which
Judging by the following::: /-- $ cygcheck --help Usage: cygcheck [OPTIONS] [program ...] -s, --sysinfo = system information (not with -k) -v, --verbose = verbose output (indented) (for -s or programs) -r, --registry = registry search (requires -s) -k, --keycheck = perform a keyboard check session (not with -s) -h, --help = give help about the info You must at least give either -s or -k or a program name $ man cygcheck No manual entry for cygcheck \-- I don't know how we'd be expected to find the -c option for cygcheck. Are there any other goodies in there? For that matter, I didn't even know cygcheck would give version numbers (although I did know setup.exe would give me that info...) --Kevin -Original Message- From: Robert Collins [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 20, 2001 7:17 AM I'm sure you could have answered the version question yourself: $ cygcheck -c which Cygwin Package Information Package Version which 1.5-1
RE: which which
Corinna - is there any pro's/cons (besides not maintaining your own version) for/against using the GNU version? J. -Original Message- From: Corinna Vinschen [mailto:[EMAIL PROTECTED]] Sent: Thursday, 20 December 2001 12:47 pm To: [EMAIL PROTECTED] Subject: Re: which which On Thu, Dec 20, 2001 at 11:23:38PM +1100, Robert Collins wrote: Ah, well I've no idea about how GNU our version is. :}. I contributed my own small version of which (which is version 1.5). If you want to maintain which in future, feel free to contribute the GNU version instead. I have actually no problems stepping back. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:[EMAIL PROTECTED] Red Hat, Inc. === 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: which which
On Thu, Dec 20, 2001 at 02:29:54PM -, Morrison, John wrote: Corinna - is there any pro's/cons (besides not maintaining your own version) for/against using the GNU version? Dunno. I never compared them. If you compare them and you're under the impression the GNU version has some real advantages, feel free to maintain that package. My which has a -a option and that's it. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] Red Hat, Inc.
RE: which which
Here's the help from the GNU one... $ which --help Usage: which [options] [--] programname [...] Options: --version, -[vV] Print version and exit successfully. --help, Print this help and exit successfully. --skip-dot Skip directories in PATH that start with a dot. --skip-tilde Skip directories in PATH that start with a tilde. --show-dot Don't expand a dot to current directory in output. --show-tilde Output a tilde for HOME directory for non-root. --tty-only Stop processing options on the right if not on tty. --all, -aPrint all matches in PATH, not just the first --read-alias, -i Read list of aliases from stdin. --skip-alias Ignore option --read-alias; don't read stdin. --read-functions Read shell functions from stdin. --skip-functions Ignore option --read-functions; don't read stdin. (please note that I'm away from Saturday until 2 Jan next year - so if I do package this it may not be for a while :) J. -Original Message- From: Corinna Vinschen [mailto:[EMAIL PROTECTED]] Sent: Thursday, 20 December 2001 3:28 pm To: '[EMAIL PROTECTED]' Subject: Re: which which On Thu, Dec 20, 2001 at 02:29:54PM -, Morrison, John wrote: Corinna - is there any pro's/cons (besides not maintaining your own version) for/against using the GNU version? Dunno. I never compared them. If you compare them and you're under the impression the GNU version has some real advantages, feel free to maintain that package. My which has a -a option and that's it. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:[EMAIL PROTECTED] Red Hat, Inc. === 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: Units
On Thu, Dec 20, 2001 at 02:09:17PM -0500, Christopher Faylor wrote: On Thu, Dec 20, 2001 at 07:38:39AM -0500, Earnie Boyd wrote: Corinna Vinschen wrote: Not amused, Corinna Nor, am I amused. If it must be tagged I'd rather see the tag NEW instead, unless the maintainer believes that it's actually an experimental version. I think I've already given my opinion on this, too. I don't see any reason for a new package to be marked Test. What's the gain? It will just result in the package getting almost no exposure. What extra information will be gained by making it Test? Will the new user be more forgiving? More apt to report bugs? I don't get it. I thought the intent of Test was to have a version of a product for people to try while still providing a safety net of a stable version to fall back to. I don't see how that applies to the first release of a new package. So back to the original question: John, are you sure that it should become a `test' version? Otherwise I'll remove it. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] Red Hat, Inc.
Re: bash completion (was: RE: Units)
Charles Wilson wrote: John, why don't you create a bashutils package, to serve as a collection of (moderately) useful bash scripts and settings. For now, it could contain only bashcompletion, but later you could add -- oh, bashprompt, or something... I'm sure every daily bash user has interesting things to contribute. Myself, I have a bunch of aliases I depend on daily, and install on every machine I get an account on. -- = ICBM Address: 36.8274040 N, 108.0204086 W, alt. 1714m
RE: Units
Hi, I think this reply is too late (since I've just downloaded it from a mirror ;), I don't mind whether it's a test version or not - but the docs are still not terribly clear wrt this (IMHO). I'll send an announcement tomorrow. Thanks, J. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Corinna Vinschen Sent: Thursday, 20 December 2001 7:26 pm To: [EMAIL PROTECTED] Subject: Re: Units On Thu, Dec 20, 2001 at 02:09:17PM -0500, Christopher Faylor wrote: On Thu, Dec 20, 2001 at 07:38:39AM -0500, Earnie Boyd wrote: Corinna Vinschen wrote: Not amused, Corinna Nor, am I amused. If it must be tagged I'd rather see the tag NEW instead, unless the maintainer believes that it's actually an experimental version. I think I've already given my opinion on this, too. I don't see any reason for a new package to be marked Test. What's the gain? It will just result in the package getting almost no exposure. What extra information will be gained by making it Test? Will the new user be more forgiving? More apt to report bugs? I don't get it. I thought the intent of Test was to have a version of a product for people to try while still providing a safety net of a stable version to fall back to. I don't see how that applies to the first release of a new package. So back to the original question: John, are you sure that it should become a `test' version? Otherwise I'll remove it. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] Red Hat, Inc.
Re: Units
- Original Message - From: Christopher Faylor [EMAIL PROTECTED] I don't see how that applies to the first release of a new package. I'd call it pretty basic risk management. If the package doesn't cause any havoc, then put it in current really quickly. I'm just nervous with the concept that any new package go directly into curr. remember that setup has prev/curr/test re-established and functional ( I still need feedback on whether the behaviour is intuitive, and to update upset to create prev and test automatically). Anyway, at the end of the day, this ain't my problem. Put stuff directly into curr. Good luck. Rob
Re: Units
On Fri, Dec 21, 2001 at 03:27:33PM +1100, Robert Collins wrote: - Original Message - From: Christopher Faylor [EMAIL PROTECTED] I don't see how that applies to the first release of a new package. I'd call it pretty basic risk management. If the package doesn't cause any havoc, then put it in current really quickly. I'm just nervous with the concept that any new package go directly into curr. But, I still don't understand what you expect to happen. Do you think that a non-adventurous person would be interested in the package but would pass on it because it says Test and would therefore potentially be saved from disaster? Or, conversely, are you expecting that there is a group of people who would be interested in downloading Test versions and providing useful feedback for first time package providers? I just think of this as It's a new package. Since it's brand new, it could have bugs. If you want people to try the package then don't put any barriers in the path of downloading it. Maybe if this was the first release of a disk optimization tool or something, I could see a need to be very careful. But, so far this discussion has been wrt a program which generates large characters and a program which converts between various systems of units. The *only* thing I can think of that would require care with packages like these would be to ensure that they didn't overwrite other parts of cygwin's installation. I can see that becoming more of an issue as time progresses. But, that's something that should be handled in software, not by end-users downloading test versions. Btw, I think Earnie's idea of having a *New!* category is actually a good one. I have been meaning to implement something like that for the web package lister, in fact. cgf
Re: Units
=== - Original Message - From: Christopher Faylor [EMAIL PROTECTED] Btw, I think Earnie's idea of having a *New!* category is actually a good one. I have been meaning to implement something like that for the web package lister, in fact. Yes. I intend to do that for setup once we have a persistent database of whats available - anything added since the last actual installation activity would be added to 'New'. Rob
Re: Units
On Fri, Dec 21, 2001 at 04:25:49PM +1100, Robert Collins wrote: === - Original Message - From: Christopher Faylor [EMAIL PROTECTED] Btw, I think Earnie's idea of having a *New!* category is actually a good one. I have been meaning to implement something like that for the web package lister, in fact. Yes. I intend to do that for setup once we have a persistent database of whats available - anything added since the last actual installation activity would be added to 'New'. It's a little more problematic for the web page, though, unless I use cookies. Mmm... cookies. cgf
Re: Units
=== - Original Message - From: Christopher Faylor [EMAIL PROTECTED] What about New within the last _x_ days ? Then it's up to the user. Rob
new setup snapshot
I've uploaded a new setup snapshot for the adventurous. w32api also has been updated, and the update is needed to build the setup HEAD code. Feedback welcome. remaining features to next release: 1) Gary's layout changes. 2) Clickable categories. 3) Pavel Tsekov's netio refactor to io_stream. Rob.
