Re: Stow 2.0.x release requirements

On Wed, Nov 16, 2011 at 11:51 AM, Adam Spiers <[email protected]> wrote:
> Anyway, here's what I intend to do next:
>
> =A0- Transplant the current savannah git master branch onto my git->cvs
> =A0 =A0import of the old CVS repository.
>
> =A0- Move Troy's experimental stuff into a separate branch and clean up
> =A0 =A0the author name/email on these commits.
>
> =A0- Where appropriate, forward-port some post-1.3.3 commits from the
> =A0 =A0old CVS repo to the head of the 2.x branch (it looks like your
> =A0 =A0rewrite was based on the 1.3.3 release rather than CVS HEAD).
>
> =A0- Fix a few other minor issues I've noticed.

These are now done.  It turned out that several of the post-1.3.3
commits weren't appropriate for forward-porting, e.g. the --ignore,
--force, and --subdir patches seem to have been superceded by other
work already in 2.0.1.

Perhaps my most pleasing achievement today was this:

perl -MTest::Harness -e 'runtests(@ARGV)' t/*.t
t/chkstow.t ................ ok
t/cleanup_invalid_links.t .. ok
t/defer.t .................. ok
t/examples.t ............... ok
t/find_stowed_path.t ....... ok
t/foldable.t ............... ok
t/join_paths.t ............. ok
t/parent.t ................. ok
t/stow_contents.t .......... ok
t/stow.t ................... ok
t/unstow_contents_orig.t ... ok
t/unstow_contents.t ........ ok
All tests successful.
Files=3D12, Tests=3D97,  1 wallclock secs ( 0.10 usr  0.04 sys +  1.15
cusr  0.17 csys =3D  1.46 CPU)
Result: PASS

However, none of the tests are running under 'use strict' / 'use
warnings', and it seems that due to use of package globals, this will
be difficult to fix before addressing one of the remaining tasks:

> =A0- Split the core code off into Stow.pm.

So I will do that next, followed by:

> =A0- Add my support for ignore list files. =A0I might send a separate
> =A0 =A0mail to this list about the design.
>
> =A0- (Maybe) port my conflict resolution code over.
>
> I've submitted a request to be part of the savannah project. =A0If
> someone gives me push access to the repo then I'll push my work.
> Otherwise I'll publish it via github.

Now available here:

  https://github.com/aspiers/stow

but be warned that it is still liable to regular rebasing.