Perl6-Pugs
view release on metacpan or search on metacpan
docs/Pugs/Doc/Hack.pod view on Meta::CPAN
please use C<util/add-svn-props.sh> to add standard Subversion properties to
your new file:
$ ./util/add-svn-props.sh newfile1 newfile2
Ideally, this is done after you add the file, but before you commit it.
It can be run later if for some reason it's run initially.
If you're on Win32 and can't run shell scripts, run C<svn> manually:
$ svn propset svn:eol-style "native" newfile1 newfile2
$ svn propset svn:mime-type "text/plain; charset=UTF-8" newfile1 newfile2
If you create a new subdirectory under C<ext/>, please remember to set the
C<svn:ignore> property to tell Subversion to ignore automatically generated
files like C<Makefile> or C<blib/>.
$ cat > /tmp/props
pm_to_blib
blibdirs
Makefile
Makefile.old
blib
$ svn propset svn:ignore -F /tmp/props ext/Your-New-Module
Except for the files in F<script/> and F<util/>, C<svn:executable> should
always be unset, even for test files.
=head2 Shebang lines
All test files should not use any shebang line, as they specify a single
runtime for the code but Perl 6 code should run under multiple runtimes,
Pugs and the v6 Perl 5 module to name two. Remember to put a C<use v6> in
the beginning of your Perl 6 programs, too, to keep perl5 from accidentally
util/add-svn-props.sh view on Meta::CPAN
else
BINARY=svk
fi
[ "$1" ] || {
echo -e "Usage: $0 file1 file2...\n # Sets the usual svn properties on the given files." >&2
exit 1
}
for i in "$@"; do
$BINARY propset svn:eol-style "native" "$i"
$BINARY propset svn:mime-type "text/plain; charset=UTF-8" "$i"
done
util/add-text-file.sh view on Meta::CPAN
BINARY=svk
fi
[ "$1" ] || {
echo -e "Usage: $0 file1 file2...\n # Adds the given files to svn as text files." >&2
exit 1
}
for i in "$@"; do
$BINARY add --non-recursive "$i"
$BINARY propset svn:eol-style "native" "$i"
$BINARY propset svn:mime-type "text/plain; charset=UTF-8" "$i"
done
( run in 1.472 second using v1.01-cache-2.11-cpan-71847e10f99 )