From: Mike Fedyk <mfedyk@matchmail.com>
To: Ragnar Kj?rstad <reiserfs@ragnark.vestdata.no>
Cc: Grant Miner <mine0057@mrs.umn.edu>, Bennett Todd <bet@rahul.net>,
reiserfs-list@namesys.com
Subject: Re: software packaging and ReiserFS v4
Date: Fri, 5 Sep 2003 13:35:47 -0700 [thread overview]
Message-ID: <20030905203547.GE19041@matchmail.com> (raw)
In-Reply-To: <20030905201806.GV31864@vestdata.no>
On Fri, Sep 05, 2003 at 10:18:06PM +0200, Ragnar Kj?rstad wrote:
> On Fri, Sep 05, 2003 at 12:44:13PM -0700, Mike Fedyk wrote:
> > On Fri, Sep 05, 2003 at 01:15:41PM -0500, Grant Miner wrote:
> > > If you are making a packaging system, I recommend you do not allow
> > > scipts, since they open up a whole can of worms. (They're impossible to
> > > invert, introduce security problems, make additional work for GUI
> > > package managers, and cause too many problems.)
> >
> > What do you replace them with then?
>
> I think if scripts were to be removed from the packaging system you
> would have to add a package-feature for every single thing that scripts
> are currently used for.
>
> If you look through a collection of packages I think you will find that
> they typically do things like:
> - create users
> - start / stop deamons
> and so on.
>
> So the package-system would need a way to specify that a user is part of
> the package (that would be very easy with a /etc/passwd.d-system) and
> that deamons that are part of the package should be started at install
> and stopped at uninstall-time.
>
> There are probably dozens of other examples of common operations - and
> you would not be able to remove the script-feature unless 99% of what
> they are used for is not needed anymore - so it's a complicated task.
Great, so now you have a scripting language in the installer. What did you
just achieve?
If you want gui integration of the scripts, just make nice wrappers of the
standard unix utilities that create a window saying "creating user x", or
prompting the user for data, or printing a notice.
You could probably even take the ncurses library, and add the wrappers there.
But let the people who want to do this choose the best way...
next prev parent reply other threads:[~2003-09-05 20:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 16:54 software packaging and ReiserFS v4 Bennett Todd
2003-09-03 21:18 ` Jürgen Botz
2003-09-03 21:37 ` Bennett Todd
2003-09-03 21:52 ` Jürgen Botz
2003-09-04 1:28 ` Bennett Todd
2003-09-04 5:05 ` Jeffrey Yasskin
2003-09-03 23:11 ` Grant Miner
2003-09-05 18:15 ` Grant Miner
2003-09-05 19:44 ` Mike Fedyk
2003-09-05 20:18 ` Ragnar Kjørstad
2003-09-05 20:35 ` Mike Fedyk [this message]
2003-09-05 20:39 ` OT: package scripts (was Re: software packaging and ReiserFS v4) Bennett Todd
2003-09-05 21:37 ` Grant Miner
2003-09-08 9:49 ` software packaging and ReiserFS v4 Nikita Danilov
2003-09-08 10:52 ` Hans Reiser
2003-09-05 7:08 ` Richard Heycock
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=20030905203547.GE19041@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=bet@rahul.net \
--cc=mine0057@mrs.umn.edu \
--cc=reiserfs-list@namesys.com \
--cc=reiserfs@ragnark.vestdata.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.