public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Geert Bevin <gbevin@theleaf.be>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] qmail and .keep files
Date: 13 Dec 2001 13:54:11 +0100	[thread overview]
Message-ID: <1008248051.1016.14.camel@willow.theleaf.office> (raw)
In-Reply-To: <1008245927.10992.6.camel@uranus.u235.eyep.net>

On Thu, 2001-12-13 at 13:18, Vitaly Kushneriuk wrote:
> I know, and as I said, looks like a VERY ugly way of doing that.

I agree that it's not pretty.

> Yet, no package should "own", in any way, the standard directories. They
> can be created form post_install of, say, base_layout, and left there
> forever. Then if a package provides /usr/bin/program, only program
> should be included in CONTENTS, not the /usr/bin. The .keep files
> can be used during build process, to indicate directories, that
> do bolong to the package, but should not be installed (better to wrap
>  this by some "dokeepdir" func, to allow future change). 
> During unmerge, only "owned" directories can be removed, 
> and only if no other installed package uses them. A file with dir names
> and usage counter can be used to track that.

I don't know if what you're proposing is a good alternative. I'll have
to think about this when I have the time. Anyway these kind of decisions
should be made by drobbins. Daniel, what are your thoughts on this
matter?

> > > Anyway, ebuild for qmail should not install them in the 
> > > queue directory, for qmail-qstat to work properly.

The problem is that when I remove them now for the qmail-qstat to
function properly, an unmerge of a previously installed package might
remove important queue dirs which are need for qmail to function. When
having to chose between the two I tend to prefer having a properly
running qmail system in all cases than an incorrectly reported number by
qstat.

> While you on it, consider attached qmail control script with many new
> options.
> Note: /init.d/svscan should be fixed not to use start-stop-daemon,
> as it does not allow for more then one copy of svscan running.
> It is better to run separate svscan in qmail/supervise dir then
> linking qmail/supervise/* to /service, as this way you have better
> control of when qmail will start.

I'll have a look at it when I get the time.

-- 
Geert Bevin
the Leaf sprl/bvba
"Use what you need"           Pierre Theunisstraat 1/47
http://www.theleaf.be         1030 Brussels
gbevin@theleaf.be             Tel & Fax +32 2 241 19 98



  reply	other threads:[~2001-12-13 12:54 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 [this message]
2001-12-13 13:13       ` Jerry A!
2001-12-13 17:45       ` [gentoo-dev] qmail and .keep files - admin consideration? jano
2001-12-13 17:47         ` 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=1008248051.1016.14.camel@willow.theleaf.office \
    --to=gbevin@theleaf.be \
    --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