Keith Marshall schreef, Op 7-9-2012 19:55:
> On 07/09/12 16:25, Erwin Waterlander wrote:
>> This means, I manually lzma my xml files,
> No. Here are the steps you should follow, after checking out a clean
> git clone from SF:
> $ cd mingw-dist
> $ autoconf
> $ mkdir build
> $ cd build
> $ ../configure
> $ make
> Only when you've done this, which creates a complete set of current
> .xml.lzma files in your build tree, should you proceed to apply any XML
> changes in the source tree; (when you do this, don't touch the issue
> numbers -- make will adjust them automatically).
> After you've applied your source changes, you run make again (in the
> build tree). This will regenerate the .xml.lzma for the sources you've
> modified; it will also collect links to everything you need to upload to
> FRS, in "unpublished" sudirectories of each build directory.
Okay, thanks. When I have write permission I will try. I just released a
>> and upload them via a browser or ftp.
> You may choose whatever method suits you best; I normally use sftp.
My favourite is lftp.
> Just be sure to upload everything which appears in your
> directories. Then, when you've confirmed that everything has been
> safely uploaded, you may delete the content of those.
>> I never looked into the mingw cvs/git repo before. But it is logical
>> that you keep the xml files under version control. It would be handy if
>> I had write permission to mingw-dist.
> Yeah, we'll sort that out for you. We'll also need to augment the
> existing .cvsignore with a .gitignore, (and perhaps also a .hgignore).
>> Or else somebody else must check in the xml files I uploaded to FRS.
> No. It's better if you can do it yourself. It's also a good idea for
> you to push promptly, (and to always pull immediately before each batch
> of updates), lest two of us happen to modify the same source within a
> common update interval, and induce an issue number race.
Okay. I'll do it.