public inbox for gentoo-java@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joshua Nichols <nichoj@gentoo.org>
To: gentoo-java@lists.gentoo.org
Subject: [gentoo-java] dealing with VM vendors that don't change distfiles names
Date: Tue, 28 Mar 2006 08:59:42 -0500	[thread overview]
Message-ID: <4429414E.8030401@gentoo.org> (raw)

It seems some of the VM vendors, mostly Sun and IBM, just love to
release new versions of their VMs, but without changing the filename
they get released as. In short, this means that it breaks our ebuilds,
because the instructions for getting the file are the same, but the file
it leads to is different, and therefore the digest breaks.

There are currently at least 3 bugs filed for this issue:

http://bugs.gentoo.org/show_bug.cgi?id=127204
http://bugs.gentoo.org/show_bug.cgi?id=123590
http://bugs.gentoo.org/show_bug.cgi?id=122220

There are a few solutions.

* Just redigest the ebuild with the new distfile. This would be the
quickest solution, but it'd be problematic because then the digest would
be broken for people that already have the distfiles.

* Have users rename the files. This is used in a few cases at least.
This leads to the question of how to version the ebuilds though, because
they don't follow a sane (to us) versioning scheme, ie GA, SR-1, SR-2, etc.

* Some totally awesome way I haven't of yet.

Thoughts?

- Josh
-- 
gentoo-java@gentoo.org mailing list



             reply	other threads:[~2006-03-28 13:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28 13:59 Joshua Nichols [this message]
2006-03-28 14:16 ` [gentoo-java] dealing with VM vendors that don't change distfiles names Miroslav Šulc
2006-03-28 22:39 ` [gentoo-java] " Wiktor Wandachowicz

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=4429414E.8030401@gentoo.org \
    --to=nichoj@gentoo.org \
    --cc=gentoo-java@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