public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: 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)))
Date: Mon, 28 Jul 2008 15:27:00 -0000	[thread overview]
Message-ID: <20080728152750.GN29031@calimero.vinschen.de> (raw)
In-Reply-To: <5f21cb61c3a7cb7ad2d02df11907792e.squirrel@mail.morrison.mine.nu>

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

  reply	other threads:[~2008-07-28 15:27 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17 15:53 New Cygwin 1.7.0-18 in release-2 Corinna Vinschen
2008-07-18  0:18 ` Eric Blake
2008-07-18  7:33   ` Corinna Vinschen
2008-07-18  7:53     ` Corinna Vinschen
2008-07-18  8:08       ` Corinna Vinschen
2008-07-18 12:07         ` Corinna Vinschen
2008-07-22 21:19           ` Corinna Vinschen
2008-07-18 16:37 ` Marco Atzeri
2008-07-18 17:08   ` Corinna Vinschen
2008-07-18 17:56     ` Christopher Faylor
2008-07-18 18:18       ` Corinna Vinschen
2008-07-18 23:59         ` Brian Dessent
2008-07-19 10:15         ` Marco Atzeri
2008-07-18 19:29 ` Bill Hoffman
2008-07-19 12:24   ` Corinna Vinschen
2008-07-19 14:16 ` Cygwin 1.7.0-19 (was Re: New Cygwin 1.7.0-18 in release-2) Corinna Vinschen
2008-07-22 17:42   ` Cygwin 1.7.0-20 (was Re: Cygwin 1.7.0-19 (was Re: New Cygwin 1.7.0-18 in release-2)) Corinna Vinschen
2008-07-25  8:10     ` Corinna Vinschen
2008-07-25 11:00       ` 1.7.0-21 broken Corinna Vinschen
2008-07-25 18:08         ` Corinna Vinschen
2008-07-28 14:52     ` 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))) John Morrison
2008-07-28 15:27       ` Corinna Vinschen [this message]
2008-07-28 16:34         ` base-[files|password] for 1.7 John Morrison
2008-07-29  9:32           ` Corinna Vinschen
2008-07-29 11:50             ` Eric Blake
2008-07-28 18:56         ` Pierre A. Humblet
2008-07-29  9:45           ` Corinna Vinschen
2008-07-29 14:35             ` Pierre A. Humblet
2008-07-29 14:53               ` Corinna Vinschen
2008-07-29 16:24                 ` Pierre A. Humblet
2008-07-29 22:22                   ` Pierre A. Humblet
2008-07-30  9:14                     ` Corinna Vinschen
2008-07-28 19:00         ` 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))) Christopher Faylor
2008-07-29 11:37         ` Eric Blake
2008-07-29 11:56           ` John Morrison
2008-07-29 12:01             ` base-[files|password] for 1.7 Eric Blake
2008-07-29 12:28               ` Corinna Vinschen
2008-07-29 14:31                 ` Christopher Faylor
2008-07-29 14:56                   ` Corinna Vinschen
2008-07-29 16:18                     ` John Morrison
2008-07-29 18:00                       ` Christopher Faylor
2008-07-30  1:39                         ` Christopher Faylor
2008-07-30  9:22                           ` Corinna Vinschen
2008-07-30 15:20                             ` Christopher Faylor
2008-07-30 17:39                               ` Corinna Vinschen
2008-07-21 23:42 ` New Cygwin 1.7.0-18 in release-2 Yaakov (Cygwin Ports)
2008-07-22  9:32   ` Corinna Vinschen
2008-07-23 17:26     ` Yaakov (Cygwin Ports)
2008-07-23 18:00       ` Corinna Vinschen
2008-07-23 20:44         ` John Morrison
2008-07-24  9:08           ` Corinna Vinschen
2008-07-24  9:18             ` John Morrison
2008-07-24  9:26               ` Corinna Vinschen
2008-07-25 10:07           ` Andrew Schulman
2008-07-24  3:45         ` Yaakov (Cygwin Ports)
2008-07-24  9:24           ` Corinna Vinschen
2008-07-24 16:18             ` Yaakov (Cygwin Ports)
2008-07-24 17:46               ` Corinna Vinschen
2008-07-31  6:57 ` Yaakov (Cygwin Ports)
2008-07-31  7:39   ` Corinna Vinschen
2008-07-31  8:28     ` Yaakov (Cygwin Ports)
2008-07-31 11:44       ` Corinna Vinschen
2008-07-31 13:00         ` Charles Wilson
2008-07-31 13:23           ` Corinna Vinschen
2008-07-31 13:31             ` Corinna Vinschen
2008-07-31 14:10               ` Corinna Vinschen
2008-07-31 20:16                 ` Corinna Vinschen
2008-07-31 15:06         ` Yaakov (Cygwin Ports)
2008-07-31 15:41           ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080728152750.GN29031@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).