public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Help testing ebuilds? golang/Fabio load balancer
Date: Mon, 13 Nov 2017 10:16:24 -0500	[thread overview]
Message-ID: <55904a6d-2e26-9820-5866-0452706c3fcb@gentoo.org> (raw)
In-Reply-To: <23048.26379.584985.594980@a1i15.kph.uni-mainz.de>

On 11/12/2017 10:21 AM, Ulrich Mueller wrote:
> 
>>   * Change the PMS to remove "undefined behavior" and replace it with
>>     "empty directories must be tracked, and may only be removed once no
>>     installed package is using them," or something along those lines.
>>     That leaves the implementation up to the PM.
> 
> How? Look up VDB entries of all installed packages? Note that this
> would have to be done for every dir that becomes empty, not just the
> ones currently containing a .keep_* file.

Not necessarily. I chose the "empty directories must be tracked" wording
to avoid that. If the PM were about to remove a directory that wasn't in
the database of empty directories, then it could proceed normally.


> What problem are you trying to solve? I see typically around 100
> .keep_* files on my systems. These are empty files, so they don't use
> any blocks. And 100 inodes system wide looks like negligible usage
> of resources to me.

If you're asking what problem I was trying to solve by leaving the
implementation up to the PM, then I was only trying not to be pushy. If
the "automatic keepdir" idea...

>   * Have portage call its keepdir code on any empty directories in $D
>     between src_install and pkg_preinst.

is workable and if the PM authors are fine with it, then we could spec that.


  reply	other threads:[~2017-11-13 15:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-10  4:08 [gentoo-dev] Help testing ebuilds? golang/Fabio load balancer Damo Brisbane
2017-11-10 12:59 ` Michael Orlitzky
2017-11-10 21:36   ` Damo Brisbane
2017-11-11  0:21     ` Michael Orlitzky
2017-11-11  7:58       ` Michał Górny
2017-11-11 17:31         ` Michael Orlitzky
2017-11-11 19:26           ` Michał Górny
2017-11-12 12:53             ` Michael Orlitzky
2017-11-12 13:43               ` Michał Górny
2017-11-13 15:10                 ` Michael Orlitzky
2017-11-12 15:21               ` Ulrich Mueller
2017-11-13 15:16                 ` Michael Orlitzky [this message]
2017-11-11 19:54           ` Brian Dolbec

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=55904a6d-2e26-9820-5866-0452706c3fcb@gentoo.org \
    --to=mjo@gentoo.org \
    --cc=gentoo-dev@lists.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