From: "marduk" <marduk@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] why do different ebuilds have the same version number?
Date: Wed, 27 Apr 2005 10:53:04 -0700 [thread overview]
Message-ID: <1114624384.32128.232858999@webmail.messagingengine.com> (raw)
In-Reply-To: <20050427130938.GG20252@ulric.rafique.org>
On Wed, 27 Apr 2005 06:09:38 -0700, "Imran Sher Rafique"
<imran@rafique.org> said:
> I hope this doesn't come across as too much of a rant.
>
> Summary
> -------
> Is it accepted practice to allow for changes in an ebuild without
> changing the
> ebuild version number?
Unfortunately yes ;-). This also has been a problem for
packages.gentoo.org code, because I basically have to make a series of
assumptions as to when an ebuild is considered "new" or "updated".
Originally I thought I could just just look at the timestamps on the
ebuilds, but that turned out to be a very bad determiniation of when an
ebuild has changed. Then I thought revision numbers, but that's
innacurate too. Basically now it comes down to looking at the current
ebuild in portage and comparing it to the last time I looked at it.
It's much more expensive, because you have to look at *every* ebuild,
not just "ebuilds changed since x date/time" or "ebuilds newer than
version y". Oh no, now I sound like I'm ranting ;-)
-m
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-04-27 17:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 13:09 [gentoo-dev] why do different ebuilds have the same version number? Imran Sher Rafique
2005-04-27 13:05 ` Caleb Tennis
2005-04-27 13:06 ` Mike Frysinger
2005-04-27 13:56 ` [gentoo-dev] " Imran Sher Rafique
2005-04-27 17:53 ` marduk [this message]
2005-04-27 19:07 ` [gentoo-dev] " Brian Harring
2005-04-27 19:17 ` Francesco Riosa
2005-04-27 19:41 ` Brian Harring
2005-04-27 20:02 ` Francesco Riosa
2005-04-27 20:25 ` Brian Harring
-- strict thread matches above, loose matches on Subject: below --
2005-04-27 20:36 Brian Harring
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=1114624384.32128.232858999@webmail.messagingengine.com \
--to=marduk@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