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 (was Re: Cygwin 1.7.0-20 (was Re: Cygwin 1.7.0-19 (was Re: New Cygwin 1.7.0-18 in release-2)))


On Jul 28 15:51, John Morrison wrote:
> On Tue, July 22, 2008 6:42 pm, Corinna Vinschen wrote:
> >   You can now call mkpasswd and mkgroup without any -l or -d parameter
> >   and both tools choose by themselves what information to print, depending
> >   on the machine being a domain member machine or not.
> >
> >   This should result in a matching change to the base-passwd package for
> >   1.7.  The /etc/postinstall/passwd-grp.sh script should call both tools
> >   without any parameter.
> >
> >   Could you please change that for us, John?
> 
> Ok, changed base-password/etc/postinstall/passwd-grp.sh to remove the
> parameters when calling mkpasswd and mkgroup.  I've left the rest of the
> script the same; that's OK?

Yep, that's ok.

> 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.

> 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?

>   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 :)

> 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 ;).

> /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.

> 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.

> I'll package and upload tomorrow evening if nobody has any improvements.

Cool, I'm looking forward,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat


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