From: "jano" <jano@portablehole.net>
To: <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] qmail and .keep files - admin consideration?
Date: Thu, 13 Dec 2001 09:45:39 -0800 (PST) [thread overview]
Message-ID: <1237.63.204.248.196.1008265539.squirrel@www.portablehole.net> (raw)
In-Reply-To: <1008248051.1016.14.camel@willow.theleaf.office>
I hope I got this right: the .keep files are there to prevent the qmail
queue directory from being clobbered during an unmerge, correct? My take on
this discussion will be obviously OT, so any response to this would best
come directly to me (unless deemed proper for gentoo-dev)
>From an administration standpoint, however, how often is qmail, on a
production box, actually updated? Some patches, e.g. smtp auth or
qmail-ldap, come out with a new version every.. say.. several months, but
that's about all I've seen. The main patches (big todo, concurrency,
tarpiting, reiser sync) haven't changed much. On a box where you're
constantly installing various qmail patches, i can see how the queue
directory issue might get in the way, but on a production box, for now, I
would simply remove those .keep files and not worry about it (either from
the ebuild before installing, or manually after install). Of course this is
a no brainer, a moot point, i feel silly having brought it up. *shrug*
Oh, but great thing about modifying an ebuild is that your modified version
is stored in /var/db/pkg :) I love that :)))
next prev parent reply other threads:[~2001-12-13 17:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 11:33 [gentoo-dev] qmail and .keep files Vitaly Kushneriuk
2001-12-13 11:39 ` Geert Bevin
2001-12-13 12:18 ` Vitaly Kushneriuk
2001-12-13 12:54 ` Geert Bevin
2001-12-13 13:13 ` Jerry A!
2001-12-13 17:45 ` jano [this message]
2001-12-13 17:47 ` [gentoo-dev] qmail and .keep files - admin consideration? Jerry A!
2001-12-13 18:24 ` Daniel Robbins
2001-12-13 18:03 ` [gentoo-dev] qmail and .keep files Daniel Robbins
2001-12-13 20:09 ` Geert Bevin
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=1237.63.204.248.196.1008265539.squirrel@www.portablehole.net \
--to=jano@portablehole.net \
--cc=gentoo-dev@gentoo.org \
/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