public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFD: Replacement for versionator.eclass in PMS (for EAPI 7?)
Date: Wed, 2 Dec 2015 12:03:32 +0100	[thread overview]
Message-ID: <20151202120332.25387828@gentoo.org> (raw)
In-Reply-To: <22106.6463.805834.391338@a1i15.kph.uni-mainz.de>

On Sat, 28 Nov 2015 22:14:39 +0100
Ulrich Mueller <ulm@gentoo.org> wrote:

> As you may know, we intend to move the functionality of
> versionator.eclass to the package manager, possibly in EAPI 7.
> The following is what mgorny and myself have come up with, see
> bug 482170 [1], especially comments 15 and 16 there.
> 
> Currently there are 15 functions defined in that eclass, and we
> believe that it will not be feasible to implement all of them.
> However, several of the functions are similar to each other and can
> be combined. Two of them, namely get_version_component_range() and
> replace_version_separator(), account for the vast majority of what
> is used by ebuilds.
> 
> We therefore think that the following three functions would be
> sufficient to cover all ebuilds' needs:

What's the point, need or advantage in moving this to all-ebuild-scope?

Usually eclass refactor/api cleanup are done in a -r{n+1} while
deprecating -rn. This would have the advantage that you can quickly
post a complete implementation and get wider reviews.


  parent reply	other threads:[~2015-12-02 11:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-28 21:14 [gentoo-dev] RFD: Replacement for versionator.eclass in PMS (for EAPI 7?) Ulrich Mueller
2015-11-29 23:23 ` Peter Stuge
2015-11-30  6:28   ` Michał Górny
2015-12-02 11:03 ` Alexis Ballier [this message]
2015-12-02 12:04   ` Ulrich Mueller
2015-12-02 12:18     ` Alexis Ballier
2015-12-07  5:37 ` Jason Zaman
2015-12-07  7:00   ` Michał Górny
2015-12-07  7:41   ` Ulrich Mueller

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=20151202120332.25387828@gentoo.org \
    --to=aballier@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