public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Help testing ebuilds? golang/Fabio load balancer
Date: Sun, 12 Nov 2017 14:43:04 +0100	[thread overview]
Message-ID: <1510494184.22960.3.camel@gentoo.org> (raw)
In-Reply-To: <1eed4490-6e21-42bf-6546-e73013d30b35@gentoo.org>

W dniu nie, 12.11.2017 o godzinie 07∶53 -0500, użytkownik Michael
Orlitzky napisał:
> On 11/11/2017 02:26 PM, Michał Górny wrote:
> > > 
> > > As far as the actual implementation goes, I'm not sure that
> > > automatically-generated ".keep" files are better than having the package
> > > manager maintain its own database. The latter would be more complex, but
> > > would avoid littering everyone's filesystems with ".keep" files.
> > 
> > Do you care enough to spec this properly, introduce EAPI-conditional
> > behavior for it and prepare patches for the package managers?
> > 
> 
> Some day -- I'll add it to my list. For now I'll update the docs to
> explain why you should use keepdir, and do a QA warning for empty
> directories.

I'm not convinced a QA warning is valid, given that not every empty
directory is meaningful. You're going to either cause people to create
unnecessary 'keepdir's, or to be swamped by false positives.

>  Then how does this sound for EAPI=next?
> 
>   * Ban keepdir.
> 
>   * Have portage call its keepdir code on any empty directories in $D
>     between src_install and pkg_preinst.

How does this account for /run and other non-persistent locations?

>   * Update the devmanual and portage documentation to suggest dodir
>     instead of keepdir in the new EAPI.
> 
>   * 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.

...and makes interoperability between different package managers
impossible, defeating the purpose of PMS in the first place.

-- 
Best regards,
Michał Górny



  reply	other threads:[~2017-11-12 13:43 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 [this message]
2017-11-13 15:10                 ` Michael Orlitzky
2017-11-12 15:21               ` Ulrich Mueller
2017-11-13 15:16                 ` Michael Orlitzky
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=1510494184.22960.3.camel@gentoo.org \
    --to=mgorny@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