maillog: 14/07/2005-00:36:15(-0700): Robin H. Johnson types
> On Thu, Jul 14, 2005 at 09:17:38AM +0200, Kevin F. Quinn wrote:
> > On 14/7/2005 7:24:03, Craig Lawson ([EMAIL PROTECTED]) wrote:
> > > [...] To be more concrete, I'm thinking of something like a database [...]
> > I don't think a separa
On Thu, Jul 14, 2005 at 09:17:38AM +0200, Kevin F. Quinn wrote:
> On 14/7/2005 7:24:03, Craig Lawson ([EMAIL PROTECTED]) wrote:
> > [...] To be more concrete, I'm thinking of something like a database [...]
> I don't think a separate database is a good idea; too many sources for
> information.
How
On 14/7/2005 7:24:03, Craig Lawson ([EMAIL PROTECTED]) wrote:
> [...] To be more concrete, I'm thinking of something like a database [...]
I don't think a separate database is a good idea; too many sources for
information.
> [...] For example [...]
> current: any
> target: =gnome-base/gno
> What I'd like to see *before* I upgrade is a list of advisories about
> what trouble I'm in for. By the time most people upgrade a package,
> someone's been there before and felt the pain. The answers, or at least
> the warnings, are in the Forums. Yet searching the forums before
> upgrading each
This past weekend, I upgraded about 80 packages and a kernel and later
discovered that my CD-ROM drive went missing and my lovingly crafted
gnome menus were trashed by Gnome 2.10 and no longer editable. Oh joy,
another portage upgrade surprise. Some rummaging around in the Gentoo
forums sent me in
