From: Keith M. <kei...@us...> - 2013-03-16 18:03:46
|
On 14/03/13 16:56, Keith Marshall wrote: > I know you're itching to get a candidate out, but I'll need to get back > to you; I'll aim to do that by end of play tomorrow. Okay. A day late, curtailed by a disk crash, here it is. First, in a local testing branch, I modified mingw-dist, per the attached diff; then, I ran 'make' on the modified tree. Second, I copied the *unpublished* modified mingw32-runtime.xml.lzma, resulting from the 'make', to a locally created and otherwise empty var/lib/mingw-get/data directory, whence I unlzma'd it and packaged it as wsl_rc-4.0-1-mingw32-rc-1-meta.tar.lzma; this, we would publish to the FRS file store; we SHOULD NOT otherwise publish this modified mingw32-runtime.xml.lzma to the online catalogue. Third, I set up a virgin Win7 sandbox directory, installed mingw-get, updated to match the current online catalogue, and installed G++. Fourth, to simulate publication of my mingw-dist changes, I copied my unpublished mingw32-wsl_rc.xml.lzma and mingw32-package-list.xml.lzma to the var/lib/mingw-get/data directory in the sandbox, and unlzma'd it in place, (as 'mingw-get update' would have done, had they been already published to the online catalogue). Fifth, to simulate the effect of publication and subsequent download, I copied my wsl_rc-4.0-1-mingw32-rc-1-meta.tar.lzma to the package cache directory within the sandbox. Sixth, to simulate availability of actual release candidate packages, I simply hard linked all existing mingwrt and w32api version-3.x packages within the cache, to similarly named packages with appropriate version adjustments. Finally, to both test and demonstrate the capabilities of this delivery technique, I ran the sequence of operations in the attached transcript. -- Regards, Keith. |