This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: initscripts package available for review/upload
The problem is in existance of configfile.default in 2 different packages
(sysvinit and initscripts). Sysvinit's /etc/inittab is almost useless,
initscript's postinstall creates a usefull one. It would be better to remove
/etc/inittab from the next sysvinit release and to replace it with
/etc/inittab.sample.
Sergey Okhapkin
Somerset, NJ
----- Original Message -----
From: "Max Bowsher" <maxb@ukf.net>
To: "Sergey Okhapkin" <sos@prospect.com.ru>; <cygwin-apps@cygwin.com>
Sent: Wednesday, November 13, 2002 5:13 PM
Subject: Re: initscripts package available for review/upload
> Sergey Okhapkin <sos@prospect.com.ru> wrote:
>
> > Creating a new inittab.default will not activate the package. That's
> > why I prefer to save an existing inittab and create a new one.
>
> /etc/inittab should absolutely not be packaged as such, because otherwise
> setup will delete it (and may therefore destroy user configuration) at
> package reinstalls/upgrades/uninstalls.
>
> The configfile.default + postinstall script copying configfile.default to
> configfile if it does not exist is a reasonably well accepted Cygwin
> packaging method. Why not do that?
>
> Max.
>