tech-toolchain archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Sets, subsets, syspkgs, and MK*

On Wed, Dec 16, 2009 at 12:28:38PM +0900, Masao Uebayashi wrote:
> > Could you show exact example of usage how global patches
> > and partial patches can be generated by MK* variable settings?
> > Users can still choose necessary patches from global one as cube says,
> > unless builders blindly generate patches from whole two sets of DESTDIR.
> I see you have a solid view how to generate binary patches.
> See below...
> > > If you create a binary patch of YP code in libc, how do you call it?
> > 
> > It's better to mention how "a binary patch of YP code in libc"
> > can or cannot be generated by MK_* or USE_* variable in your idea.
> Problem here is, I can't apply "YP code in libc" patch if I disable *_YP.
> I can't apply any libc patch if TNF decides to enable *_YP by default.

Why on earth would anyone who built their own binaries want to apply
a binary patch from TNF?  This is beyond crazy, there are so many ways
this can go wrong.

Quentin Garnier - -
"See the look on my face from staying too long in one place
[...] every time the morning breaks I know I'm closer to falling"
KT Tunstall, Saving My Face, Drastic Fantastic, 2007.

Attachment: pgp5mxZ5m2jsb.pgp
Description: PGP signature

Home | Main Index | Thread Index | Old Index