Re: Suggestions to setup.exe
On 3 April 2011 03:44, Larry Hall (Cygwin) wrote: On 4/2/2011 12:44 PM, Tony wrote: Hi. I just installed this package here which brought with it a ton of dependancies. Why can't setup.exe, when I want to uninstall this package, also uninstall all the dependancies? Please make the next Cygwin release support clean uninstalls. That's not as easy as it might initially sound. Uninstalling all dependencies might result in other utilities not working, since these dependencies could be shared. Determining the dependencies to install is easier than determining those that are safe to uninstall. So that's by way of explanation for why you see the behavior you currently see from 'setup.exe' when uninstalling a package. That said, it is possible to figure out which dependencies could safely be uninstalled. It depends. ;) When uninstalling a package, it sure makes sense to uninstall all the packages that depend on it, since they would stop working anyway. So for example, removing the libX11 runtime would be a quick way to remove all X11 programs. However, removing a package because an uninstalled package depends on is not generally a good idea, even if no other package depends on it. That's because the user might still require it, either directly or perhaps through a program they've built from source. For example, mintty depends on cygutils (for its postinstall script), but removing mintty doesn't mean that the user no longer wants to run cygstartCo. Other package managers address this by keeping a record of which packages were requested explicitly by the user and which were installed implicitly as dependencies of other packages. Even then, the user might come to depend on packages that were only installed implicitly, so there's still scope for uninstalling packages accidentally, but at least there's a simple remedy: explicitly request such packages and it won't happen again. In any case, improving support for uninstalling stuff isn't exactly a new suggestion, and as usual, the real problem is: http://www.cygwin.com/acronyms/#SHTDI Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Suggestions to setup.exe
On 4/2/2011 12:44 PM, Tony wrote: Hi. I just installed this package here which brought with it a ton of dependancies. Why can't setup.exe, when I want to uninstall this package, also uninstall all the dependancies? Please make the next Cygwin release support clean uninstalls. That's not as easy as it might initially sound. Uninstalling all dependencies might result in other utilities not working, since these dependencies could be shared. Determining the dependencies to install is easier than determining those that are safe to uninstall. So that's by way of explanation for why you see the behavior you currently see from 'setup.exe' when uninstalling a package. That said, it is possible to figure out which dependencies could safely be uninstalled. That part of your request could be implemented in the future. -- Larry _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Suggestions for 'chere' package
Da Idiocrat wrote: I was wondering if there was any way to get chere to add an entry to the context menu when you right-click the BACKGROUND of Windows Explorer so that I don't have to go to the parent folder just to open Cygwin shell in the folder I want? Maybe I missed an option or something? I know it's not important but it really annoyed me... You can right-click the icon of explorer window to get the context menu of the current directory. Regards, Frank -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Suggestions for 'chere' package
Check out the Subject: using chere thread from June 2007 in this list. I think what you are requesting is discussed there and why is not implemented. Da Idiocrat wrote: Hey everyone, I downloaded chere since I wanted to get an Open Bash Here menu item to make things easier, but uninstalled it because it didn't work out for me. I was wondering if there was any way to get chere to add an entry to the context menu when you right-click the BACKGROUND of Windows Explorer so that I don't have to go to the parent folder just to open Cygwin shell in the folder I want? Maybe I missed an option or something? I know it's not important but it really annoyed me... So I uninstalled chere-1.0.1 and I had to make a .reg file to add this functionality instead, but I'm just wondering if there is a way to do it in chere instead, since I don't like messing around in the registry myself. Just curious, Julian S. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Suggestions for 'chere' package
Da Idiocrat wrote: I downloaded chere since I wanted to get an Open Bash Here menu item to make things easier, but uninstalled it because it didn't work out for me. Sorry to hear that. I was wondering if there was any way to get chere to add an entry to the context menu when you right-click the BACKGROUND of Windows Explorer so that I don't have to go to the parent folder just to open Cygwin shell in the folder I want? Maybe I missed an option or something? I know it's not important but it really annoyed me... Please see the thread Paul Mallas identified. There is also an older thread discussing this (2006ish). So I uninstalled chere-1.0.1 and I had to make a .reg file to add this functionality instead, but I'm just wondering if there is a way to do it in chere instead, since I don't like messing around in the registry myself. I'd be interested in hearing the advantage of your .reg files over the chere script, and how it accomplishes it. The scripts should be able to duplicate anything that a .reg file does. Thanks, Dave. chere maintainer. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Suggestions for 'chere' package
Dave wrote: Da Idiocrat wrote: I downloaded chere since I wanted to get an Open Bash Here menu item to make things easier, but uninstalled it because it didn't work out for me. Sorry to hear that. I was wondering if there was any way to get chere to add an entry to the context menu when you right-click the BACKGROUND of Windows Explorer so that I don't have to go to the parent folder just to open Cygwin shell in the folder I want? Maybe I missed an option or something? I know it's not important but it really annoyed me... Please see the thread Paul Mallas identified. There is also an older thread discussing this (2006ish). So I uninstalled chere-1.0.1 and I had to make a .reg file to add this functionality instead, but I'm just wondering if there is a way to do it in chere instead, since I don't like messing around in the registry myself. I'd be interested in hearing the advantage of your .reg files over the chere script, and how it accomplishes it. The scripts should be able to duplicate anything that a .reg file does. A disadvantage of .reg files is that some organizations have windows policies that require administrator rights to use regedit.exe; .ref files don't work for non-administrators (like me). And so I need to give a BIG THANKS to the people who wrote regtool.exe and the code for /proc/registry/, and also the setup.exe coders who remembered to give us a just for me option. - Barry -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Suggestions for cygcheck
On Tue, 18 Jul 2006, Bengt-Arne Fjellner wrote: Hi I would like to suggest that cygcheck file should know about symlinks i.e. $ ls -la `which xmgrace` lrwxrwxrwx 1 Administratör Användare 32 Jul 18 16:37 /usr/bin/xmgrace - /usr/share/grace/bin/xmgrace.exe* $ cygcheck xmgrace # now gives Found: C:\cygwin\bin\xmgrace.exe C:/cygwin/bin/xmgrace.exe $ cygcheck xmgrace # Suggested behaviour Found: C:\cygwin\bin\xmgrace.exe which is a symlink to /usr/share/grace/bin/xmgrace.exe Or something like that I recall making a patch for this. I'll dig it out, and see if it's been submitted, or if it still needs more work. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte. But no -- you are no fool; you call yourself a fool, there's proof enough in that! -- Rostand, Cyrano de Bergerac -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Suggestions for caching only DNS server to run on CygWin
On Thu, Apr 27, 2006 at 08:28:20PM -0500, Herb Martin wrote: Suggestions for caching only DNS server to run on CygWin If you are looking for a relay DNS server, consider dnrd. Look it up on Sourceforge. It is ported to cygwin (I helped!). -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Suggestions for caching only DNS server to run on CygWin
Herb Martin wrote: Suggestions for caching only DNS server to run on CygWin I'm not exactly sure what you're getting at here. I use the win32 native version of BIND9 for this and it works great. It's not really running on Cygwin, but I don't see what that has to do with anything. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Suggestions for caching only DNS server to run on CygWin
Herb Martin wrote: Suggestions for caching only DNS server to run on CygWin Like Brian said, bind works fine, either compiled under Cygwin or the binary distributed by ISC. -- René Berber -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Suggestions for caching only DNS server to run on CygWin
On Thu, Apr 27, 2006 at 09:22:26PM -0500, Ren? Berber wrote: Herb Martin wrote: Suggestions for caching only DNS server to run on CygWin Like Brian said, bind works fine, either compiled under Cygwin or the binary distributed by ISC. And, moreover complete sentences which frame well-formed thoughts are also -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: suggestions for cygwin developers
Alex Goldman wrote: When Cygwin gets set up, it would be more user-friendly if it placed two icons on the desktop: one should start maximized Rxvt; another should start X with a couple of xterms or whatever. First-time users might think that the MS-DOS terminal is as good as it gets, and this is not good for Cygwin. Others still have to figure out how to start Rxvt automatically and how to configure it to look pretty. Also, it would be neat to be able to keep Cygwin up-to-date automatically. How about a prompt when a new Cygwin DLL version is available: A new version of Cygwin is available. Run setup to install the latest version. This could be included as part of the /etc/profile or something. Chris -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: suggestions for cygwin developers
Chris January wrote:
Alex Goldman wrote:
When Cygwin gets set up, it would be more user-friendly if it placed
two icons on the desktop:
one should start maximized Rxvt; another should start X with a couple
of xterms or whatever.
First-time users might think that the MS-DOS terminal is as good as it
gets, and this is not good for Cygwin. Others still have to figure out
how to start Rxvt automatically and how to configure it to look
pretty.
Also, it would be neat to be able to keep Cygwin up-to-date
automatically.
How about a prompt when a new Cygwin DLL version is available:
A new version of Cygwin is available. Run setup to install the latest
version.
This could be included as part of the /etc/profile or something.
Chris
Checking to see if a new version available assumes an internet connection.
My opinion is that this would play havoc with dial-up users.
If this is something you want, here is a hack to accomplish it.
I'm sure there are better, cleaner ways to do this and it will break
as soon as something in the package list changes, but it's 5 am
and I am not ready to think yet.
#!/bin/bash
#Igor's whichpkg
function whichpkg() {
wget -qO- http://cygwin.com/cgi-bin2/package-grep.cgi?grep=$1; | \
sed -ne '/Cygwin Package List/,${s#/\?[^]*##g;p}'
}
LATEST=`whichpkg cygwin | grep emulation | tail -1 | awk -F -
'{print $2}'`
CUR=`uname -a | awk '{print $3}' | awk -F( '{print $1}'`
if [ $CUR != $LATEST ]; then
echo new cygwin dll version $LATEST available
else
echo Your cygwin dll is current
fi
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: suggestions for cygwin developers
On Thu, 28 Jul 2005, Ken Dibble wrote:
Chris January wrote:
Alex Goldman wrote:
When Cygwin gets set up, it would be more user-friendly if it placed
two icons on the desktop:
one should start maximized Rxvt; another should start X with a
couple of xterms or whatever.
First-time users might think that the MS-DOS terminal is as good as
it gets, and this is not good for Cygwin. Others still have to
figure out how to start Rxvt automatically and how to configure it
to look pretty.
Also, it would be neat to be able to keep Cygwin up-to-date
automatically.
How about a prompt when a new Cygwin DLL version is available:
A new version of Cygwin is available. Run setup to install the latest
version.
This could be included as part of the /etc/profile or something.
Chris
Checking to see if a new version available assumes an internet
connection. My opinion is that this would play havoc with dial-up users.
Agreed. I would guess it could be a small service (a nice implementation
would even put an icon in the system tray).
If this is something you want, here is a hack to accomplish it.
I'm sure there are better, cleaner ways to do this and it will break
as soon as something in the package list changes, but it's 5 am
and I am not ready to think yet.
While the effort of actually writing code at 5am is commendable
(especially since you said yet -- the only time you'd see *me* writing
code at 5am is if I'd been doing it all night :-) ), the code below does
do some wasteful things.
#!/bin/bash
#Igor's whichpkg
function whichpkg() {
wget -qO- http://cygwin.com/cgi-bin2/package-grep.cgi?grep=$1; | \
sed -ne '/Cygwin Package List/,${s#/\?[^]*##g;p}'
}
You could also simply 'wget -qO- http://cygwin.com/packages/cygwin;' and
find the last line that starts with cygwin. That would be *wa-ay*
faster.
LATEST=`whichpkg cygwin | grep emulation | tail -1 | awk -F - '{print
$2}'`
Even if you do use the whichpkg above, it's probably better to search
for 'cygwin1\.dll'... :-)
Besides, this would lose the Cygwin-specific release number.
CUR=`uname -a | awk '{print $3}' | awk -F( '{print $1}'`
CUR=`uname -r | awk -F( '{print $1}'`
or
CUR=`cygcheck -cd cygwin | sed -ne 's/^cygwin\s\+// p'`
Both will not do the right thing if you have a snapshot installed. You'll
have to think about what exactly the right thing is in this case.
if [ $CUR != $LATEST ]; then
echo new cygwin dll version $LATEST available
else
echo Your cygwin dll is current
fi
Again, you need to also deal with snapshots.
But if this were written in C, run as a service, and extended to all
installed packages, it could be the beginning of something useful. :-)
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!
If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
RE: suggestions for cygwin developers
Original Message
From: Ken Dibble
Sent: 28 July 2005 11:48
Checking to see if a new version available assumes an internet connection.
My opinion is that this would play havoc with dial-up users.
Besides, who wants cygwin to phone home? That's waaay too much like
windoze!
If this is something you want, here is a hack to accomplish it.
I'm sure there are better, cleaner ways to do this and it will break
as soon as something in the package list changes, but it's 5 am
and I am not ready to think yet.
#!/bin/bash
#Igor's whichpkg
function whichpkg() {
wget -qO- http://cygwin.com/cgi-bin2/package-grep.cgi?grep=$1; | \
sed -ne '/Cygwin Package List/,${s#/\?[^]*##g;p}'
}
LATEST=`whichpkg cygwin | grep emulation | tail -1 | awk -F -
'{print $2}'`
CUR=`uname -a | awk '{print $3}' | awk -F( '{print $1}'`
if [ $CUR != $LATEST ]; then
echo new cygwin dll version $LATEST available
else
echo Your cygwin dll is current
fi
Here's my hack, which extracts LATEST from the cygwin.com frontpage list
of dll release announcements:
LATEST=`wget -q -O - http://cygwin.com/ | grep New Cygwin DLL | sed -e
's/^.*New Cygwin DLL \([0-9.-_]*\).*$/\1/' | head -1`
...after that you'd set CUR and compare them in the same way.
cheers,
DaveK
--
Can't think of a witty .sigline today
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: suggestions for cygwin developers
Igor Pechtchanski wrote:
On Thu, 28 Jul 2005, Ken Dibble wrote:
Chris January wrote:
Alex Goldman wrote:
When Cygwin gets set up, it would be more user-friendly if it placed
two icons on the desktop:
one should start maximized Rxvt; another should start X with a
couple of xterms or whatever.
First-time users might think that the MS-DOS terminal is as good as
it gets, and this is not good for Cygwin. Others still have to
figure out how to start Rxvt automatically and how to configure it
to look pretty.
Also, it would be neat to be able to keep Cygwin up-to-date
automatically.
How about a prompt when a new Cygwin DLL version is available:
A new version of Cygwin is available. Run setup to install the latest
version.
This could be included as part of the /etc/profile or something.
Chris
Checking to see if a new version available assumes an internet
connection. My opinion is that this would play havoc with dial-up users.
Agreed. I would guess it could be a small service (a nice implementation
would even put an icon in the system tray).
If this is something you want, here is a hack to accomplish it.
I'm sure there are better, cleaner ways to do this and it will break
as soon as something in the package list changes, but it's 5 am
and I am not ready to think yet.
While the effort of actually writing code at 5am is commendable
(especially since you said yet -- the only time you'd see *me* writing
code at 5am is if I'd been doing it all night :-) ), the code below does
do some wasteful things.
#!/bin/bash
#Igor's whichpkg
function whichpkg() {
wget -qO- http://cygwin.com/cgi-bin2/package-grep.cgi?grep=$1; | \
sed -ne '/Cygwin Package List/,${s#/\?[^]*##g;p}'
}
You could also simply 'wget -qO- http://cygwin.com/packages/cygwin;' and
find the last line that starts with cygwin. That would be *wa-ay*
faster.
LATEST=`whichpkg cygwin | grep emulation | tail -1 | awk -F - '{print $2}'`
Even if you do use the whichpkg above, it's probably better to search
for 'cygwin1\.dll'... :-)
Besides, this would lose the Cygwin-specific release number.
CUR=`uname -a | awk '{print $3}' | awk -F( '{print $1}'`
CUR=`uname -r | awk -F( '{print $1}'`
or
CUR=`cygcheck -cd cygwin | sed -ne 's/^cygwin\s\+// p'`
Both will not do the right thing if you have a snapshot installed. You'll
have to think about what exactly the right thing is in this case.
if [ $CUR != $LATEST ]; then
echo new cygwin dll version $LATEST available
else
echo Your cygwin dll is current
fi
Again, you need to also deal with snapshots.
But if this were written in C, run as a service, and extended to all
installed packages, it could be the beginning of something useful. :-)
Igor
Yes, I know it was wasteful. I guess I failed to make my point.
OPINION: I don't believe in having the latest and greatest of
everything. I believe
in STABLE ( as anyone who has looked at my cygcheck
will attest).
So, like I said, I really don't think something
like this belongs in cygwin proper.
POINT: I can see the downside to this and have great reservations.
But if YOU must have this, it shouldn't be too hard for
YOU to do it.
YMMV.
Igor, Thanks for continuing to enlighten me about the myriad of ways of
doing things.
Regards,
Ken
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: suggestions for cygwin developers
On Wed, 27 Jul 2005, Alex Goldman wrote: When Cygwin gets set up, it would be more user-friendly if it placed two icons on the desktop: one should start maximized Rxvt; another should start X with a couple of xterms or whatever. First-time users might think that the MS-DOS terminal is as good as it gets, and this is not good for Cygwin. Others still have to figure out how to start Rxvt automatically and how to configure it to look pretty. This doesn't have to be done at the level of the Cygwin setup. You could easily write a package (or a set of packages) that would place such icons on the desktop (see, for example, the gold-star-winning chere package). Also, it would be neat to be able to keep Cygwin up-to-date automatically. Just run setup.exe regularly, and it will pick up the latest packages. Of course, you may need to reboot if you do this concurrently with using Cygwin processes, so this will need to be thought through very well. The main point is: Cygwin is a volunteer effort. If you feel that some feature would be beneficial, consider contributing it. If it's done well, others will like it, and it could be included into the official set of packages. Simply suggesting a feature rarely results in it being contributed by someone else. 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! If there's any real truth it's that the entire multidimensional infinity of the Universe is almost certainly being run by a bunch of maniacs. /DA -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: suggestions for cygwin developers
On 7/27/05, Igor Pechtchanski [EMAIL PROTECTED] wrote: On Wed, 27 Jul 2005, Alex Goldman wrote: When Cygwin gets set up, it would be more user-friendly if it placed two icons on the desktop: one should start maximized Rxvt; another should start X with a couple of xterms or whatever. First-time users might think that the MS-DOS terminal is as good as it gets, and this is not good for Cygwin. Others still have to figure out how to start Rxvt automatically and how to configure it to look pretty. This doesn't have to be done at the level of the Cygwin setup. You could easily write a package (or a set of packages) that would place such icons on the desktop (see, for example, the gold-star-winning chere package). Also, it would be neat to be able to keep Cygwin up-to-date automatically. Just run setup.exe regularly, and it will pick up the latest packages. Of course, you may need to reboot if you do this concurrently with using Cygwin processes, so this will need to be thought through very well. The main point is: Cygwin is a volunteer effort. If you feel that some feature would be beneficial, consider contributing it. If it's done well, others will like it, and it could be included into the official set of packages. Simply suggesting a feature rarely results in it being contributed by someone else. Igor As Tyler Durden said, You decide your own level of involvement. My commitment to Cygwin is not great enough to contribute to it. I just started using it. Tomorrow, I might decide I prefer FreeBSD and VMWare or Windows Services. Anyway, if user feedback is not appreciated, none will be forthcoming. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: suggestions for cygwin developers
On Wed, 27 Jul 2005, Alex Goldman wrote: On 7/27/05, Igor Pechtchanski [EMAIL PROTECTED] wrote: On Wed, 27 Jul 2005, Alex Goldman wrote: When Cygwin gets set up, it would be more user-friendly if it placed two icons on the desktop: one should start maximized Rxvt; another should start X with a couple of xterms or whatever. First-time users might think that the MS-DOS terminal is as good as it gets, and this is not good for Cygwin. Others still have to figure out how to start Rxvt automatically and how to configure it to look pretty. This doesn't have to be done at the level of the Cygwin setup. You could easily write a package (or a set of packages) that would place such icons on the desktop (see, for example, the gold-star-winning chere package). Also, it would be neat to be able to keep Cygwin up-to-date automatically. Just run setup.exe regularly, and it will pick up the latest packages. Of course, you may need to reboot if you do this concurrently with using Cygwin processes, so this will need to be thought through very well. The main point is: Cygwin is a volunteer effort. If you feel that some feature would be beneficial, consider contributing it. If it's done well, others will like it, and it could be included into the official set of packages. Simply suggesting a feature rarely results in it being contributed by someone else. Igor As Tyler Durden said, You decide your own level of involvement. My commitment to Cygwin is not great enough to contribute to it. I just started using it. Tomorrow, I might decide I prefer FreeBSD and VMWare or Windows Services. Anyway, if user feedback is not appreciated, none will be forthcoming. Your preferences are, of course, up to you. And user feedback is duly noted and recorded in the mailing list archives -- perhaps someone will get interested enough to implement it. I just wanted to make sure your expectations regarding said feedback reflect the actual state of affairs. :-) 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! If there's any real truth it's that the entire multidimensional infinity of the Universe is almost certainly being run by a bunch of maniacs. /DA -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Suggestions
On Sat, 4 Dec 2004 21:22:14 -0600 (CST), Rodrigo de Salvo Braz wrote: I would like to suggest that the words Keep, Prev, Curr and Exp be changed in the Cygwin Setup. I believe they are too abbreviated when there is room for clearer words. But, more importantly, I believe that the choice of words Keep and Curr is a bit confusing. Keep without saying what is being kept suggests little and Curr may be interpreted as the version currently installed in the computer (which is actually the meaning of Keep), not the packages' currently released versions. Just a thought. Any suggestions for clearer words? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Suggestions
-Original Message- From: cygwin-owner On Behalf Of Joshua Daniel Franklin Sent: 06 December 2004 14:58 On Sat, 4 Dec 2004 21:22:14 -0600 (CST), Rodrigo de Salvo Braz wrote: I would like to suggest that the words Keep, Prev, Curr and Exp be changed in the Cygwin Setup. I believe they are too abbreviated when there is room for clearer words. But, more importantly, I believe that the choice of words Keep and Curr is a bit confusing. Keep without saying what is being kept suggests little and Curr may be interpreted as the version currently installed in the computer (which is actually the meaning of Keep), not the packages' currently released versions. Just a thought. Any suggestions for clearer words? How about Keep, Revert, Stable and Unstable? cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Suggestions
On Mon, 6 Dec 2004, Joshua Daniel Franklin wrote: On Sat, 4 Dec 2004 21:22:14 -0600 (CST), Rodrigo de Salvo Braz wrote: I would like to suggest that the words Keep, Prev, Curr and Exp be changed in the Cygwin Setup. I believe they are too abbreviated when there is room for clearer words. But, more importantly, I believe that the choice of words Keep and Curr is a bit confusing. Keep without saying what is being kept suggests little and Curr may be interpreted as the version currently installed in the computer (which is actually the meaning of Keep), not the packages' currently released versions. Just a thought. Any suggestions for clearer words? I meant just the full words, really, especially for Exp (I keep thinking Exponential :-). Personally, I would choose the following replacements for Keep and Curr: Keep - Installed version Curr - Up-to-date version Best, Rodrigo -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Suggestions
On Fri, 3 Dec 2004, Rodrigo de Salvo Braz wrote: Hi, Is there some more specific place in which to give suggestions or feedback about the Cygwin pages? Nope. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Suggestions
-Original Message- From: cygwin-owner On Behalf Of Brian Ford Sent: 05 December 2004 20:53 To: Rodrigo de Salvo Braz Cc: cygwin Subject: Re: Suggestions On Fri, 3 Dec 2004, Rodrigo de Salvo Braz wrote: Hi, Is there some more specific place in which to give suggestions or feedback about the Cygwin pages? Nope. Yes, there is! But first you gotta get a href=http://cygwin.com/acronyms#WJM;mean!/href[*] And then you gotta get up, you got to get up out of your chair, and go to the window. Open it, and stick your head out, and yell, I'm mad as hell, and I'm not going to take Cygwin any more! cheers, DaveK [*] Sigh. All my funniest posts get barfed by the list's spam filters because they mistake them for HTML. -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Suggestions
At 06:43 PM 12/3/2004, you wrote: Hi, Is there some more specific place in which to give suggestions or feedback about the Cygwin pages? Sure. Here. :-) See http://cygwin.com/lists.html for more details. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Suggestions
On Sat, 4 Dec 2004, Larry Hall wrote: At 06:43 PM 12/3/2004, you wrote: Is there some more specific place in which to give suggestions or feedback about the Cygwin pages? Sure. Here. :-) Ok, just making sure, thanks. I would like to suggest that the words Keep, Prev, Curr and Exp be changed in the Cygwin Setup. I believe they are too abbreviated when there is room for clearer words. But, more importantly, I believe that the choice of words Keep and Curr is a bit confusing. Keep without saying what is being kept suggests little and Curr may be interpreted as the version currently installed in the computer (which is actually the meaning of Keep), not the packages' currently released versions. Just a thought. Thanks, Rodrigo -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
