This is the mail archive of the cygwin-apps mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: base-[files|password] for 1.7


On Mon, July 28, 2008 4:27 pm, Corinna Vinschen wrote:
> On Jul 28 15:51, John Morrison wrote:
>> On Tue, July 22, 2008 6:42 pm, Corinna Vinschen wrote:
> Yep, that's ok.

Good :)

>> Do we still want the base-files profile to have the message wrt group
>> names of mkpassword/mkgroup/mkgroup_l_d?
>
> Hmm, well, it doesn't hurt a lot, right?  Using the new mkpasswd and
> mkgroup will probably reduce printing this message a lot, if not
> entirely.

Doesn't hurt, but might speed up startup by a second or so... prob not
worth removing.

>> Are there any other changes wanted?  For example, I think a comment
>> about
>> MAKE_MODE=Unix came up on the lists a few months ago...  Now's a good
>> time
>> to alter anything.
>
> Is that MAKE_MODE thingy supported at all in latest make?  If so,
> isn't MAKE_MODE=unix default anyway?

absolutely no idea.

>>   Corinna; you use the tcsh shell don't you (I seem to
>> recall)?  Are there any profile defaults we should put in for it?
>
> Yes, I'm using tcsh, but your scripts don't have to care for them
> since everything's already done in csh.login and csh.cshrc.  Including
> setting MAKE_MODE=unix :)

Ok.  So the tcsh script includes csh.cshrc?  Should the bash package
include the bash.bashrc?

>> My Debian /etc/profile sets EDITOR=vim useful?  (not if you've not
>> installed vim I suppose; vi?)
>
> I think setting EDITOR should be a user choice, but I'm not strongly
> opposing the idea, especially given that I'm vim user anyway ;).

Me too, but the user can always override this in their ~ files.

>> /etc/bash.bashrc has the following in both Debian and Ubuntu (not a
>> suprise I suppose);
>>
>> # check the window size after each command and, if necessary,
>> # update the values of LINES and COLUMNS.
>> shopt -s checkwinsize
>>
>> would it work in cygwin?  Also;
>
> Looks like bash on Cygwin doesn't set LINES and COLUMNS.  Eric?
>
>> # if the command-not-found package is installed, use it
>> if [ -x /usr/lib/command-not-found ]; then
>>         function command_not_found_handle {
>>                 # check because c-n-f could've been removed in the
>> meantime
>>                 if [ -x /usr/lib/command-not-found ]; then
>>                    /usr/bin/python /usr/lib/command-not-found -- $1
>>                    return $?
>>                 else
>>                    return 127
>>                 fi
>>         }
>> fi
>
> Not for me.

Ah, but I bet you've got just about everything installed anyway!  You also
know where/how to find this informtion.  We could knockup a script which
calls http://cygwin.com/cgi-bin2/package-grep.cgi?grep=<command>, cleans
up the html and writes it out?  It's more for the person who doesn't know
what package to install.  It'd be even easier if there was a plain text
version of the output then it'd just be curl :)  Is the source for the
package-grep.cgi available?

>> Should we have a /etc/motd?  (not that I know what should calls/displays
>> it in the cygwin env; /etc/profile?)
>
> We get a default /etc/motd when the inetutils package has been installed.

Okie, I've only installed base on my vm.

>> I'll package and upload tomorrow evening if nobody has any improvements.
>
> Cool, I'm looking forward,

Np, sorry it's take so long :(

J.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]