Re: WSL-4.0 release candidate

On 02/03/13 16:41, Earnie Boyd wrote:
> How about:
>
> rc_mingwrt-4.0-1-mingw32-rc-1-dev.tar.lzma
>
> or
>
> mingwrt-4.0-1-rc_mingw32-rc-1-dev.tar.lzma
>
> Would either of these produce the result I'm looking for?

Either may, but the former is unacceptable.

> Which is better?

The latter, but it's far from ideal; (I'm not even certain that it will 
work reliably).

> With the second the profile.xml file would need to be adjusted by the
> user to add the directory location for the rc_mingw32 system but the
> package name is the same.

Which may be awkward for the user, but at least it doesn't exhibit the 
failing of...

> With the first the user has a new package name.

...a new, and therefore independent package, which deliberately causes 
conflict with the existing mingwrt-*-mingw32-...; Chuck invested a lot 
of effort into convincing me that this is ultimately unworkable.

> Should it rather be a mix of both:
> rc_mingwrt-4.0-1-rc_mingw32-rc-1-dev.tar.lzma?

No.  Definitely not.  What about the following (untested) alternative?

* In its own XML catalogue, create a definition for a wsl-candidate 
package; this will be a dummy package, delivering only a replacement for 
var/lib/mingw-get/data/mingw32-runtime.xml itself, (as payload of 
wsl-candidate-4.0-1-mingw32-rc-1-xml.tar.xz, say).

* Add a reference for this new catalogue to mingw32-package-list.xml

* Publish the new catalogue, and the updated package list.

* Make a private local copy of mingw32-runtime.xml, (perhaps within a 
private local git branch of mingw-dist).

* Add your "release" specs for mingwrt-4.0 and w32api-4.0, as if you 
were making a formal release; DO NOT PUBLISH THIS!

* In your working directory, (taking care not to destroy anything you 
really want to keep):

    rm -rf var
    mkdir -p var/lib/mingw-get/data
    sed s/@YYYYMMDDNN@/ZZZZZZZZZZ/ mingw32-runtime.xml \
      > var/lib/mingw-get/data/mingw32-runtime.xml
    tar cf - var | xz -c > wsl-candidate-4.0-1-mingw32-rc-1-xml.tar.xz

* Publish the resultant tarball.

Now, users may opt in to testing your candidate, by running:

    mingw-get update
    mingw-get install mingw32-wsl-candidate
    mingw-get upgrade mingw32-mingwrt mingw32-w32api

and may opt out again, by:

    mingw-get remove mingw32-wsl-candidate
    mingw-get upgrade --reinstall mingw32-mingwrt mingw32-w32api

(with the caveat, for GUI users, that they must use the CLI to perform 
these operations).

-- 
Regards,
Keith.

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb