> James E Keenan wrote:
>>
>> For portability reasons, however, shouldn't it be converted to Perl 5?
>
> The difference here is that you can only generate Debian packages on a
> Debian-based system, so portability to non-Linux systems isn't a concern.
>
That was my assumption. (Along with the need
James E Keenan wrote:
For portability reasons, however, shouldn't it be converted to Perl 5? I
don't think we proceed on the assumption that all our target OSes can
handle shell.
The difference here is that you can only generate Debian packages on a
Debian-based system, so portability to no
Allison Randal wrote:
Alan Rocker wrote:
I've attached a quickie shell script, in case that's what you want.
It's a
naive little thing, but I think you'll be amused by its presumption.
Good start. Committed in r24479, with a small change to run it from the
top-level directory instead of tool
Alan Rocker wrote:
I've attached a quickie shell script, in case that's what you want. It's a
naive little thing, but I think you'll be amused by its presumption.
Good start. Committed in r24479, with a small change to run it from the
top-level directory instead of tools/dev. A little extra po
>
> A quick cage cleaner task. Create a script to generate the file
> ports/debian/parrot-doc.docs
I've attached a quickie shell script, in case that's what you want. It's a
naive little thing, but I think you'll be amused by its presumption.
A properly formatted and tested Perl script will take
