From: "Hannu E K Nevalainen \(garbage mail\)" <garbage_collector@telia.com>
To: <cygwin@cygwin.com>
Subject: RE: SUGGESTION wrt preremove / postinstall / preinstall (RE: [FAQ]Packages reported as "Incomplete" by "cygcheck -c")
Date: Mon, 22 Sep 2003 08:55:00 -0000 [thread overview]
Message-ID: <NGBBLLIAMFLGJEOAJCCEOEGFDEAA.garbage_collector@telia.com> (raw)
In-Reply-To: <1064192432.24990.27.camel@localhost>
> From: Robert Collins
>
> In general, setup needs to be taught about classes of files:
> configuration files vs image files vs data and script files.
>
> Once that general concept is in place, we can:
> * support rpm and dpkg formats more effectively
> * add classes for things like apache
> * be smarter about rebasing
>
> etc etc etc
I'm sure this is the way to go... I'm not that intimate with the details of
how setup works.
My idea was based on a wish to "clean up" - for the moment.
I didn't expect it to become a "long time solution" :-)
/Hannu E K Nevalainen, B.Sc. EE - 59°16.37'N, 17°12.60'E
-- UTC+01, DST -> UTC+02 --
--END OF MESSAGE--
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2003-09-22 8:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 17:18 [FAQ] Packages reported as "Incomplete" by "cygcheck -c" Igor Pechtchanski
2003-09-21 22:51 ` SUGGESTION wrt preremove / postinstall / preinstall (RE: [FAQ] Packages reported as "Incomplete" by "cygcheck -c") Hannu E K Nevalainen (garbage mail)
2003-09-21 23:21 ` Igor Pechtchanski
2003-09-22 3:52 ` Robert Collins
2003-09-22 8:55 ` Hannu E K Nevalainen (garbage mail) [this message]
2003-09-22 10:02 ` SUGGESTION wrt preremove / postinstall / preinstall (RE: [FAQ]Packages " Robert Collins
2003-09-22 9:00 ` SUGGESTION wrt preremove / postinstall / preinstall (RE: [FAQ] Packages " Hannu E K Nevalainen (garbage mail)
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=NGBBLLIAMFLGJEOAJCCEOEGFDEAA.garbage_collector@telia.com \
--to=garbage_collector@telia.com \
--cc=cygwin@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).