From: Darren Kirby <bulliver@badcomputer.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Re: how thorough is #emerge --sync?
Date: Wed, 18 Oct 2006 11:30:40 -0700 [thread overview]
Message-ID: <200610181130.40432.bulliver@badcomputer.org> (raw)
In-Reply-To: <15910968.RmOYfFVDSC@work.message-center.info>
Quoth the Alexander Skwar
> Darren Kirby <bulliver@badcomputer.org>:
> > Quoth the Alexander Skwar
> >
> >> · maxim wexler <blissfix@yahoo.com>:
> >> >>digg2ogg
> >> >
> >> > should be dir2ogg
> >>
> >> 0.8 is the latest stable version. Why do you think, that a different
> >> version should be offered, when you "emerge dir2ogg"?
> >
> > Well, I'm the upstream author, and _I_ think there should be different
> > (ie: newer) version offered. Good enough?
>
> No, not good enough, as that doesn't matter at all. All that matters is,
> what's in the tree. And the latest stable version is 0.8, no matter what
> you think. The question remains: Why should a different version be offered?
>
> Alexander Skwar
> --
> A closed mouth gathers no foot.
Sorry Alexander, I just don't get where you're going with this. Version 0.8
was released September 27, 2004! There have been 4 major new releases since
then, which include many bug fixes, and new and improved features. 0.8 is old
and busted, 0.9.3 is the new hotness!
Surely I don't need to explain the concept of how software improves with new
development? You're not using GCC 2.95 and kernel 2.2.10 are you?
Confused by your remarks,
-d
--
darren kirby :: Part of the problem since 1976 :: http://badcomputer.org
"...the number of UNIX installations has grown to 10, with more expected..."
- Dennis Ritchie and Ken Thompson, June 1972
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-18 18:33 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 3:37 [gentoo-user] how thorough is #emerge --sync? maxim wexler
2006-10-18 3:43 ` maxim wexler
2006-10-18 5:30 ` [gentoo-user] " Alexander Skwar
2006-10-18 5:53 ` Darren Kirby
2006-10-18 6:11 ` Iain Buchanan
2006-10-18 6:31 ` [gentoo-user] " Alexander Skwar
2006-10-18 18:30 ` Darren Kirby [this message]
2006-10-18 18:57 ` Willie Wong
2006-10-18 19:20 ` Darren Kirby
2006-10-18 21:37 ` [gentoo-user] " Alexander Skwar
2006-10-18 21:31 ` Alexander Skwar
[not found] ` <200610181449.12060.bulliver@badcomputer.org>
2006-10-19 10:04 ` [gentoo-user] " Alexander Skwar
2006-10-19 14:38 ` Devon Miller
2006-10-19 14:53 ` [gentoo-user] " Alexander Skwar
2006-10-19 17:21 ` [gentoo-user] Re: Re: " Willie Wong
2006-10-19 19:37 ` [gentoo-user] " Darren Kirby
[not found] ` <200610191217.17509.bulliver@badcomputer.org>
2006-10-19 21:16 ` [gentoo-user] [OT] " Justin Findlay
2006-10-18 21:27 ` [gentoo-user] Re: Re: " Alexander Skwar
2006-10-18 7:56 ` [gentoo-user] " Neil Bothwick
2006-10-18 18:23 ` Darren Kirby
2006-10-18 21:38 ` [gentoo-user] " Alexander Skwar
2006-10-18 3:44 ` [gentoo-user] " Brett I. Holcomb
2006-10-18 3:46 ` Brett I. Holcomb
2006-10-18 3:56 ` Drew
2006-10-18 4:00 ` Darren Kirby
2006-10-18 21:02 ` maxim wexler
2006-10-18 21:35 ` Darren Kirby
2006-10-19 0:06 ` maxim wexler
2006-10-19 10:09 ` Bo Ørsted Andresen
2006-10-19 18:23 ` Darren Kirby
2006-10-19 20:49 ` Daniel Barkalow
2006-10-18 21:49 ` Daniel Barkalow
2006-10-18 21:50 ` Neil Bothwick
2006-10-19 0:21 ` b.n.
2006-10-18 5:29 ` [gentoo-user] " Alexander Skwar
2006-10-18 8:01 ` [gentoo-user] " Neil Bothwick
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=200610181130.40432.bulliver@badcomputer.org \
--to=bulliver@badcomputer.org \
--cc=gentoo-user@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