public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Skwar <listen@alexander.skwar.name>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: Re: Re: how thorough is #emerge --sync?
Date: Wed, 18 Oct 2006 23:37:26 +0200	[thread overview]
Message-ID: <6148881.54eBfg2ClA@m-id.message-center.info> (raw)
In-Reply-To: 200610181220.23071.bulliver@badcomputer.org

· Darren Kirby <bulliver@badcomputer.org>:

> Quoth the Willie Wong
>> On Wed, Oct 18, 2006 at 11:30:40AM -0700, Darren Kirby wrote:
>> > > > 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?
>> >
>> > 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!
>>
>> Guys,
>>
>> Just to prevent the heat from escalating, may I offer my observation
>> that the two of you seems to be arguing about completely different
>> things?
> 
> Heat? I'm not mad, just confused ;)
> 
>> Alexander (and I, likewise) probably misunderstood Darren's question
>> from the start: when he posted, I thought his expectation that "emerge
>> dir2ogg" should bring in a newer version than what was offered was a
>> lack of understanding of how the portage tree works (well, some of my
>> friends do actually think that the package management system [aptget,
>> rpm, portage, etc.] would actually be smart enough to automatically
>> go on the internet and find and install the latest version of a
>> program, so I wouldn't put any misconception past human capacity).
> 
> Please note Willie, I am not the original poster. I jumped in here because I 
> wrote the script that the OP is asking about, and I agree the current stable 
> version is long outdated.
> 
> That said, I _do_ realize that the OP was asking a flawed question. I was 
> simply responding to Alexander: "Why do you think, that a different version 
> should be offered, when you "emerge dir2ogg"?".

But with a wrong answer :) In the tree, the latest stable is 0.8, check
out: <http://packages.gentoo.org/search/?sstring=dir2ogg>. There *IS*
no 0.9.3. Granted, there *should* be a 0.9.3 version, but there just
isn't. And stable is 0.8, not even 0.9.2.

As I wrote: Why does he think, that a different version than 0.8 should
be offered, when he runs "emerge dir2ogg"?

> If he means "why should portage automatically go grab the newest upstream 
> version", then I agree with his implication: it shouldn't.

That's what I wrote, yes.

> That's not what he  
> wrote though.

It is.

> The wording of his comment reads like he is asking why portage  
> should offer a more current version of the software,

That's what I asked maxim. Why does he think, that a different version,
than the latest stable in-tree-version (ie. 0.8) should be offered
when he runs "emerge dir2ogg"?

Alexander Skwar
-- 
All I ask is a chance to prove that money can't make me happy.


-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-10-18 21:54 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
2006-10-18 18:57           ` Willie Wong
2006-10-18 19:20             ` Darren Kirby
2006-10-18 21:37               ` Alexander Skwar [this message]
2006-10-18 21:31             ` [gentoo-user] " 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=6148881.54eBfg2ClA@m-id.message-center.info \
    --to=listen@alexander.skwar.name \
    --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