I had to switch from a simple self-cooked build system to quilt (
So, quilt applied says:
#57476-pdb-version.patch
#57546-tags-xemacs.patch
39742-installed-conflict.patch
56544-install_files.patch
57006-opengl-cyg.patch -p0
58034-config_args.patch
56554-make-install-lang.patch
56998-cygdll_versioning.patch -p0
quilt series says additionally:
56996-fhs-runtime.patch
57548-CONDITIONED_LINE_enh.patch
51944-README_cygwin.patch
So the next release will have some of the old patches applied -
0.6.4 Locally applied patches:
[perl #51944] [DOCS] Cygwin Readme
[perl #56562] [PATCH] root.in: add cygwin importlib
[perl #56544] [PATCH] install_files.pl
[perl #56558] [PATCH] pdb rename to parrot_pdb
[perl #56998] [TODO] rename cygwin dll to cygparrot.dll
[perl #57006] [PATCH] add cygwin opengl config quirks
[perl #57110] [PATCH] ncurses for cygwin
[perl #57112] [PATCH] postgres for cygwin
[perl #57114] [PATCH] urm RealBin issue
[perl #57296] [TODO] make install -C languages
but several new ones, which were enhancements of the old way to make parrot build to proper installables.
0.7.0 - Locally applied patches:
[perl #39742] [BUG] installed conflict
[perl #51944] [DOCS] Cygwin Readme
[perl #56544] [PATCH] install_files.pl
[perl #56998] [PATCH] rename cygwin dll to cygparrot$MAJOR_$MINOR_$PATCH.dll
[perl #57006] [PATCH] add cygwin opengl config quirks
[perl #56554] [TODO] make install -C languages
[perl #58034] [TODO] config_args
[perl #56996] [TODO] FHS runtime paths
These patches of mine are not stable enough:
56996-fhs-runtime.patch
Still working on library.c getting the
interpreter INTERPINFO_RUNTIME_PREFIX or CONFIG_HASH and check
for the new "installed" key if present.
57548-CONDITIONED_LINE_enh.patch
works fine, but too early. needs some feedback for this.
I'm also working on a draft/pdd30_install.pod.
chromatic said, that I should get the contributor license agreement sent to the foundation, but this letter still needs a stamp.
My current patches are at http://code.google.com/p/cygwin-rurban/source/browse/#svn/trunk/release/parrot/patches>, the commit at
I have one blocking test: t/pmc/namespace_65.pir which also failed for others, see
I don’t want to switch to git yet.
Why is that? (Not saying you should. Just want to know what is keeping you away.)
Re: Why not git yet
rurban on 2008-08-18T05:57:03
Because quilt is doing fine for this job, of keeping a series of patches.
git would be fine if I had a public server, if branches would get big.I just have a list of patches to keep track of until they are applied, and the number of patches is quite large.
Maintaining seperate git branches for all these little patches is overkill.And quilt feels to be the natural tool for this. series and applied is just a simple text file.
Soon I'll get parrot commit access so the dirty quilt times are over, and I will branch.
