On Wed, Feb 1, 2006 at 18:31:12 +0100, [EMAIL PROTECTED] wrote:
> Hi all.
>
> Please welcome Markus to the team.
I'm a bit late for this, but still: welcome, Markus! It's great to have
you eventually on the team (assuming you still join text-markup, of
course).
Regards,
Alexandre
pgpKWf88xyn
On Tue, 2006-01-31 at 12:15 -0800, Donnie Berkholz wrote:
> I finally came up with an idea for this that satisfies my desire to not
> recompile the package to get e.g. a logrotate file. Have the flag
> control whether it's installed to /etc or to /usr/share/doc.
+1
signature.asc
Description: Th
This is your monthly friendly reminder ! Same bat time (typically the
2nd Thursday once a month), same bat channel (#gentoo-council @
irc.freenode.net) !
If you have something you'd wish for us to chat about, maybe even
vote on, let us know ! Simply reply to this e-mail for the whole
Gentoo dev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
lo,
On Tuesday 31 January 2006 17:24, Ciaran McCreesh wrote:
> | That is surely a "cost" people have for upgrading an application and
> | have implicitly accepted by doing so.
>
> Not really. There's a basic cost of installing or upgrading an
> applic
On Wed, 01 Feb 2006 00:25:25 -0800 Donnie Berkholz
<[EMAIL PROTECTED]> wrote:
| Mark Loeser wrote:
| > I don't really see why anyone that is marking an ebuild stable
| > needs to have a fatal error because an older version of that
| > package isn't ported yet. We are perfectly capable of mentionin
Andreas Vinsander wrote:
Alin Nastac wrote:
Well, the only reason squid installs a cron/logrotate file is because of
the sentence your package ... is supposed to "just work" for the
end-user, which at that moment I understood it as a requirement.
Without it, a fresh squid install needs to be t
Alin Nastac wrote:
Well, the only reason squid installs a cron/logrotate file is because of
the sentence your package ... is supposed to "just work" for the
end-user, which at that moment I understood it as a requirement.
Without it, a fresh squid install needs to be tweaked by the user
(unless
Mark Loeser wrote:
> I don't really see why anyone that is marking an ebuild stable needs to have
> a fatal error because an older version of that package isn't ported yet. We
> are perfectly capable of mentioning this on the bug so the maintainer can fix
> it later :) A flag to ignore it will mak