From: Enrico Weigelt <weigelt@metux.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [bugzilla-daemon@gentoo.org: [Bug 326991] Testing release of sys-libs/zlib-1.2.5.3 from unofficial sources (???)]
Date: Tue, 6 Jul 2010 22:11:43 +0200 [thread overview]
Message-ID: <20100706201143.GC8603@nibiru.local> (raw)
In-Reply-To: <1278407527.1268.692.camel@tablet>
* Peter Volkov <pva@gentoo.org> schrieb:
> Enrico I don't see why we may need to maintain separate ebuilds for
> programs with patches scheduled upstream.
This all is part of a bigger strategy, we've already discussed here.
See: http://www.metux.de/download/oss-qm-project-2010050101.pdf
> Submit important patches separately or, better,
The whole idea is getting rid of individual patches, instead use a
modern VCS. If you don't like to take the METUX.* branches, I'll be
lucky to open (and even maintain) separate GENTOO.* branches.
> work with upstream so we'll get everything with next upstream release.
Actually, I'm already doing so for quite some time now.
But often cannot/doesnt want to apply hotfixes ad-hoc. That's what
OSS-QM for: provide downstream branches for distros, embedded
maintainers, etc.
cu
--
---------------------------------------------------------------------
Enrico Weigelt == metux IT service - http://www.metux.de/
---------------------------------------------------------------------
Please visit the OpenSource QM Taskforce:
http://wiki.metux.de/public/OpenSource_QM_Taskforce
Patches / Fixes for a lot dozens of packages in dozens of versions:
http://patches.metux.de/
---------------------------------------------------------------------
prev parent reply other threads:[~2010-07-06 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 23:29 [gentoo-dev] [bugzilla-daemon@gentoo.org: [Bug 326991] Testing release of sys-libs/zlib-1.2.5.3 from unofficial sources (???)] Enrico Weigelt
2010-07-06 0:07 ` Nirbheek Chauhan
2010-07-06 9:12 ` Peter Volkov
2010-07-06 20:11 ` Enrico Weigelt [this message]
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=20100706201143.GC8603@nibiru.local \
--to=weigelt@metux.de \
--cc=gentoo-dev@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