public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Iain Buchanan <iaindb@netspace.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: how thorough is #emerge --sync?
Date: Wed, 18 Oct 2006 15:41:13 +0930	[thread overview]
Message-ID: <1161151873.9922.37.camel@orpheus> (raw)
In-Reply-To: <200610172253.27152.bulliver@badcomputer.org>

On Tue, 2006-10-17 at 22:53 -0700, Darren Kirby wrote:
> 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? 

Can't argue with that *lol* can I call you UPSTREAM? ;)

This is what I do in cases like this (not aimed at UPSTREAM, but for
anyone's reference :)

1. look in /usr/portage to see if newer ebuild exists.
   - if it does, find out whether it's in ~x86, or hard masked, and
decide if I want to explicitly unmask it (usually I do).

2. if no ebuild exists, check bugs.gentoo.org and see if anyone has
requested it / submitted an ebuild that I can put in my overlay.

3. if not, I look at the app's homepage and see if I really want / need
the latest features, and if so I submit a version bump request on
bugs.gentoo.org, providing as much help in the testing process as I can.

4. if it's a very popular app, like gnome, then I look for unofficial
ebuilds and put them in my overlay.

If you try any of these options (unmask, overlay, or unofficial ebuild),
then be prepared for issues / bugs.  But that's what the game is all
about :)

HTH,
-- 
Iain Buchanan <iaindb at netspace dot net dot au>

In order to discover who you are, first learn who everybody else is;
you're what's left.

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-10-18  6:15 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 [this message]
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               ` [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=1161151873.9922.37.camel@orpheus \
    --to=iaindb@netspace.net.au \
    --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