| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
This avoids errors like
fatal: You are pushing to remote 'savannah', which is not the upstream of
your current branch 'master', without telling me what to push
to update which remote branch.
|
| | |
|
| | |
|
| |
|
|
|
| |
2.3.0 was a big release with lots of stuff, but most releases will
be smaller, so default to not having a ToC.
|
| |
|
|
| |
Avoid extra noise when exporting to text for a release announcement.
|
| | |
|
| |
|
|
| |
docker builds break ./Build dist, so do it earlier.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Under emacs, this was previously rendered as
'--no-folding'
This disables any further *note tree folding:: or *note tree
refolding::. If a new subdirectory is encountered whilst stowing a
which looks awkward. Similarly under info(1):
'--no-folding'
This disables any further *note tree folding:: or *note tree
refolding::. If a new subdirectory is encountered whilst stowing a
The new way is undesirably repetitive, but at least grammatically
correct. I don't think there's a better solution with texinfo :-/
|
| | |
|
| |\
| |
| | |
cli.t: test with the right Perl executable
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
t/cli.t calls scripts which run with the first perl found in the
user's PATH (usually the system perl), not with the perl used for the
build, as reported here:
https://rt.cpan.org/Ticket/Display.html?id=129944
Thanks to Slaven Rezic for spotting this and reporting it!
|
| | | |
|
| |/
|
|
|
|
| |
It doesn't make sense to have docs online relating to a release which
isn't yet available; it's less confusing to have a small time window
in which the online docs are out of date.
|
| |\
| |
| | |
Remove dependencies on Hash::Merge and Clone::Choose
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
stow 2.3.0 added external runtime dependencies on Hash::Merge and
Clone::Choose. Historically stow hasn't had runtime dependencies other
than Perl itself, which is a useful property if you're managing the
installation of Perl using stow; the bootstrapping instructions in
stow's manual would need updating to describe how to install these two
modules (and any dependencies they have now or in the future) as well.
However, Hash::Merge is much more general than stow actually needs, so
replace the merge() call with a few lines of equivalent code -- this
avoids the external dependencies, and is clearer than the merge()
call.
Many thanks to Adam Sampson for this patch:
https://lists.gnu.org/archive/html/bug-stow/2019-06/msg00001.html
|
| |/ |
|
| |\
| |
| | |
Maintainer tweaks
|
| | |
| |
| |
| |
| | |
Forgot to do this prior to the release :-( But at least it will
be mentioned in the announcement on the mailing lists.
|
| | |
| |
| |
| |
| | |
Run org-convert-to-odd-levels on NEWS and set local variables so
that sections can easily be exported for release announcements.
|
| | |
| |
| |
| | |
Docker generates a whole bunch of files as root.
|
| | | |
|
| |/ |
|
| |
|
|
|
| |
This allows changing which Perls are used etc. without
re-bootstrapping perlbrew.
|
| |\
| |
| | |
Use Clone backend for Hash::Merge, not Storable
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Need to avoid Storable backend, since it can't deal with regexps:
https://rt.perl.org/Public/Bug/Display.html?id=50608
This should fix the Docker builds.
|
| |/ |
|
| |\
| |
| | |
Make testing within Docker containers easier
|
| |/ |
|
| |\
| |
| | |
Allow make to fail if missing modules for test dependencies
|
| |/
|
|
|
|
|
| |
e.g. make STRICT_TESTS=1
However we don't need this in .travis.yml as explained in the
comments.
|
| |\
| |
| | |
Dockerfile: fix Debian jessie sources
|
| |/
|
|
| |
https://superuser.com/questions/1423486/issue-with-fetching-http-deb-debian-org-debian-dists-jessie-updates-inrelease
|
| |\
| |
| | |
Make docker scripts use get-version
|
| | | |
|
| |\ \
| |/
|/| |
rebuild META.* in preparation for 2.3.0 release
|
| |/ |
|
| |\
| |
| | |
Various improvements to tests
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
.stowrc can be obtained from $HOME and/or the current working
directory; however only the $HOME case was tested before, because
during tests Stow was being run from $HOME.
So switch $TEST_DIR to an absolute path, create a new run_from/
subdirectory, and chdir to that before invoking any Stow code. This
allows us to test the behaviour of .stowrc in $HOME and run_from/
separately.
|
| | |
| |
| |
| | |
This makes the tests and any failures more readable.
|
| | |
| |
| |
| | |
Watch out for a corner case probably only relevant in tests.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
No need for a custom function here.
|
| |/
|
|
| |
This is a more accurate reflection of what it is.
|
| |\
| |
| | |
Avoid dereferencing $ENV{HOME} if it is undefined
|
| | | |
|
| |\ \
| | |
| | | |
Improve the history of individual contributions and repositories
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The source code has been through a rather complicated journey, and
it's occasionally useful to understand this history from CVS to a
private Subversion repository to its current location in git. So
document this more thoroughly, and ensure that everyone involved
is in the THANKS file.
|
