From: Dan Naumov <jago@telefragged.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Very bad ebuild-writing practice.
Date: Sat, 17 Aug 2002 19:09:05 +0300 [thread overview]
Message-ID: <20020817190905.66977331.jago@telefragged.com> (raw)
I've just found something that I personally consider very bad ebuild-writing practice and filled a bug-report about it at: http://bugs.gentoo.org/show_bug.cgi?id=6642 I also think, it's worth pointing out to some who don't visit BugZilla, as I consider the issue to be rather important:
=================================
app-games/quakeforge/quakeforge-0.5.0.ebuild claims to provide the users with a 0.5.0 release. The 0.5.0 release does NOT even exist. The only thing that exists is a 0.5 development branch, from which, a 0.5.0 release will be eventually made.
SRC_URI="http://www.quakeforge.org/files/quakeforge-current.tar.bz2" points to a CVS snapshot that's autogenerated every hour without going through any kind of QA. Since when do we allow ebuilds to point at hourly CVS snapshots of a development tree of a program that is undergoing heavy changes ?! If you emerge quakeforge using that ebuild, it might refuse to compile because the tree is broken at that very moment. It might compile, but the compile options have changed making the ebuild somewhat obsolete. And even if it compiles, it *WILL* break, because it's expected of it, it's a development tree.
Bad. Bad. Bad.
=================================
Sincerely,
Dan Naumov aka Jago
next reply other threads:[~2002-08-17 16:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-17 16:09 Dan Naumov [this message]
2002-08-17 16:30 ` [gentoo-dev] Very bad ebuild-writing practice Jeremiah Mahler
2002-08-17 16:48 ` Dan Naumov
2002-08-17 18:40 ` Blake Watters
2002-08-17 18:52 ` mike
2002-08-18 15:44 ` Alexander Gretencord
2002-08-19 4:40 ` Troy Dack
2002-08-19 5:30 ` [gentoo-dev] " Paul
2002-08-17 16:50 ` [gentoo-dev] " Bart Verwilst
2002-08-17 17:03 ` Dan Naumov
2002-08-17 18:12 ` mike
2002-08-17 18:32 ` Dan Naumov
2002-08-19 1:13 ` Charles Lacour
2002-08-19 20:04 ` Paul de Vrieze
2002-08-17 19:13 ` Jose Alberto Suarez Lopez
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=20020817190905.66977331.jago@telefragged.com \
--to=jago@telefragged.com \
--cc=gentoo-dev@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