public inbox for debugedit@sourceware.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: debugedit@sourceware.org
Subject: Please raise version number above RPM releases
Date: Sun, 27 Jun 2021 08:36:42 +0200	[thread overview]
Message-ID: <2b049bab787602c9bb5a42c9b39187a78ffbc241.camel@gentoo.org> (raw)

Hello,

We've been packaging the RPM's debugedit executable as 'debugedit'
since 2006.  This means that the versions of debugedit packages
in Gentoo have corresponded to RPM releases.

Now, we'd like to switch to your version.  However, the problem is that
you've restarted versioning -- at least from our perspective.  If we
added debugedit-0.3 to Gentoo today, it would be seen as an older
version that the 'old' debugedit-4.16.1.3 (i.e. rpm's debugedit).

There are hacks around this but they're all particularly ugly.  Hence,
I'm wondering if it wouldn't be too much of a hassle to you to raise
the version number above the current RPM version, i.e. version 5.* or
6.* (if you take rpm5 into consideration, it is pretty dead though).

While I do realize the problem's on our end, it's non-trivial to fix
because of backwards compatibility requirements we have.  And as I said,
workarounds are particularly ugly and confusing, so I'd rather avoid
them if possible.

TIA for your consideration.

-- 
Best regards,
Michał Górny



             reply	other threads:[~2021-06-27  6:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-27  6:36 Michał Górny [this message]
2021-07-02 10:36 ` Mark Wielaard
2021-07-02 10:39   ` Michał Górny
2021-07-02 10:41     ` Mark Wielaard
2021-07-02 10:43       ` Michał Górny

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=2b049bab787602c9bb5a42c9b39187a78ffbc241.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=debugedit@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).