From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] python-2.7 && python-updater
Date: Sun, 27 Mar 2011 21:05:45 +0100 [thread overview]
Message-ID: <20110327210545.02ec5dac@digimed.co.uk> (raw)
In-Reply-To: <AANLkTim+By48Ypn772tpsjbX5+dSoZ-pEqvTg7ym092T@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
On Sun, 27 Mar 2011 12:50:57 -0700, Mark Knecht wrote:
> > I've also been hit by the first, as I think I mentioned. As for the
> > other two, re-emerging a binary package won't help at all, because
> > it's a binary package, so you unpack it rather than rebuild it.
> > That's more a problem with using binary packages on a source distro
> > than a fault of python-updater itself.
>
> Understood and agreed. For OO I couldn't quite get up the interest to
> start building from scratch though. Something like 450MB of things to
> download and then what, do it again in a week or two? Not worth it for
> my needs.
That shouldn't be a problem with the release frequency of OOo, with LO
that's more of a problem.
At least with OOo/LO you get a better program for the effort of
compiling, the open source version of VirtualBox is crippled :(
--
Neil Bothwick
Any sufficiently advanced bug is indistinguishable from a feature.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-03-27 20:07 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 0:11 [gentoo-user] python-2.7 && python-updater Mark Knecht
2011-03-25 0:28 ` Dale
2011-03-25 3:42 ` Amankwah
2011-03-25 4:48 ` Paul Hartman
2011-03-25 9:37 ` Dale
2011-03-25 9:50 ` Neil Bothwick
2011-03-25 13:56 ` Mark Knecht
2011-03-25 14:26 ` Neil Bothwick
2011-03-25 18:14 ` [gentoo-user] humor: " James
2011-03-25 14:33 ` [gentoo-user] " Roman Zilka
2011-03-25 16:44 ` Dale
2011-03-25 14:33 ` Paul Hartman
2011-03-25 16:46 ` Dale
2011-03-28 13:22 ` KH
2011-03-28 15:02 ` Mark Knecht
2011-03-28 15:41 ` Roman Zilka
2011-03-29 8:26 ` KH
2011-03-25 13:02 ` [gentoo-user] " Simon Siemonsma
2011-03-25 16:50 ` Dale
2011-03-25 19:09 ` [gentoo-user] " Stéphane Guedon
2011-03-25 19:21 ` Grant
2011-03-25 20:38 ` Neil Bothwick
2011-03-26 19:10 ` Mark Knecht
2011-03-26 19:22 ` Mick
2011-03-26 19:56 ` Mark Knecht
2011-03-26 20:36 ` Bill Longman
2011-03-26 20:53 ` Mark Knecht
2011-03-26 21:12 ` Mick
2011-03-26 21:16 ` Neil Bothwick
2011-03-26 21:33 ` Mark Knecht
2011-03-26 23:06 ` Adam Carter
2011-03-27 0:44 ` Neil Bothwick
2011-03-27 15:26 ` Mark Knecht
2011-03-27 15:47 ` Jacques Montier
2011-03-27 19:25 ` Neil Bothwick
2011-03-27 19:50 ` Mark Knecht
2011-03-27 20:05 ` Neil Bothwick [this message]
2011-03-28 0:45 ` Adam Carter
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=20110327210545.02ec5dac@digimed.co.uk \
--to=neil@digimed.co.uk \
--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