Dear Toan,
a t2 tree only has one set of current versions, so this kind of per version
patches is not generally needed. When the package is updated and the patch no
longer applies, it is just discarded - otherwise the tree would also grow to an
even more exhausting clutter to maintain, navigate, and exchange.
Would be great if you could contribute said patches so we all have them in the
trunk!
Greetings,
René
On 25.04.2011, at 17:38, Toan Pham wrote:
>
>
> Hi,
>
>
> While working on the development branch, I notice that there are some
> critical patches needed to be added to the tree. For example, to name a few
> packages that would require these packages:
>
>
> apache - apache server 2.2.17 crashes on post method (ref. bug 61384:
> https://qa.mandriva.com/show_bug.cgi?id=61384)
> aufs2 - aufs2 failed to compiler with kernel 2.6.38.2
>
>
> I believe the best method to apply these patches to the development branch
> would be creating & applying them conditional based on package version
> number. This way, patches that are added to the global package config do
> not conflict with future package updates. Patches should be put to a folder,
> for example @ package/network/apache/2.2.17/patch_gcc_segfault.patch . This
> is a better method for writing build-hooks and applying them conditionally.
> There may be a better method to do this already. If so, please share.
>
>
> -toan
>
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [email protected] with a subject of: unsubscribe t2
--
René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin
http://exactcode.com | http://t2-project.org | http://rene.rebe.de
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
