Re: [lfs-dev] Patching LFS XML sources: SVN insight required

2019-04-01 Thread thomas via lfs-dev
Am 2019-03-31 18:25, schrieb DJ Lucas via lfs-dev: On 3/30/2019 9:04 PM, Kevin Buckley via lfs-dev wrote: What's not been clear to me in trying to store changes within my local SVN repo is how to seperate things out so that for example, i could apply a "PkgUser" SVN diff to a vanilla LFS XML

Re: [lfs-dev] Patching LFS XML sources: SVN insight required

2019-03-31 Thread DJ Lucas via lfs-dev
On 3/30/2019 9:04 PM, Kevin Buckley via lfs-dev wrote: What's not been clear to me in trying to store changes within my local SVN repo is how to seperate things out so that for example, i could apply a "PkgUser" SVN diff to a vanilla LFS XML source tree if it hadn't had Thomas's Multilib patch

Re: [lfs-dev] Patching LFS XML sources: SVN insight required

2019-03-31 Thread DJ Lucas via lfs-dev
On 3/31/2019 2:38 AM, Thomas Trepl via lfs-dev wrote: Next step will be to make a branch in the original repository for the ML part. This should probably be done sooner rather than later, there is enough of a demand that it is useful outside of the core group of developers, and I'm not

Re: [lfs-dev] Patching LFS XML sources: SVN insight required

2019-03-31 Thread Thomas Trepl via lfs-dev
Am Sonntag, den 31.03.2019, 10:04 +0800 schrieb Kevin Buckley via lfs- dev: > Hi there, > > I'd be interested in some feedback, should anyone have a chance to > look at things, as to how best to leverage SVN to add "mutiple > rendering pathways", so let me expand on that. > > The build system

[lfs-dev] Patching LFS XML sources: SVN insight required

2019-03-30 Thread Kevin Buckley via lfs-dev
Hi there, I'd be interested in some feedback, should anyone have a chance to look at things, as to how best to leverage SVN to add "mutiple rendering pathways", so let me expand on that. The build system for the vanilla LFS book already has the ability to branch on SysV or SysD. Thomas's patch