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: update_etc_shells gone from cygport?
Date: Wed, 31 Aug 2016 08:29:00 -0000	[thread overview]
Message-ID: <20160831082905.GA5897@calimero.vinschen.de> (raw)
In-Reply-To: <8b37782f-eee9-47e7-3582-b4391b64c6a4@cygwin.com>

[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]

On Aug 30 11:44, Yaakov Selkowitz wrote:
> On 2016-08-30 11:15, Achim Gratz wrote:
> > Corinna Vinschen writes:
> > > > update_etc_shells /bin/tcsh /bin/csh
> > > > 
> > > > But I think we need to coordinate this with an updated base-cygwin.
> > > 
> > > base-cygwin?  Not base-files?
> > 
> > The file /etc/shells is currently installed by base-files from
> > /etc/defaults/etc/shells unless it had been altered.  So if you invent a
> > mechanism to alter the contents of the file, /etc/shells will cease to
> > be handled in pre-remove and post-install of base-files automatically,
> > I'd think.  We could then remove it of course.
> 
> Yes, /etc/shells would end up staying once altered by update_etc_shells, but
> I don't see an issue with that.

Ok, guys, give the word when you do this.

Yaakov, if you want to do it during my absence I announced on
cygwin-developers, feel free to rebuild the tcsh package.  I pick up the
new cygport file when I'm back.


Thanks,
Corinna

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2016-08-31  8:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-29 12:40 Chris Sutcliffe
2016-08-29 18:05 ` Yaakov Selkowitz
2016-08-30 12:48   ` Corinna Vinschen
2016-08-30 15:17     ` Yaakov Selkowitz
2016-08-30 15:45       ` Corinna Vinschen
2016-08-30 15:54         ` Yaakov Selkowitz
2016-08-30 16:15         ` Achim Gratz
2016-08-30 16:44           ` Yaakov Selkowitz
2016-08-31  8:29             ` Corinna Vinschen [this message]

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=20160831082905.GA5897@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).