dummy package for new portfile

[Bryan Blackburn]

On Thu, Oct 30, 2008 at 02:17:36PM -0700, Jordan K. Hubbard said:
> This has been requested before, and doesn't seem a bad idea, though one 
> alternate approach might be to add a "template" command to port(1).  Then 
> you would just say "port template > mynewportfile" and not have to go 
> looking for the template buried somewhere in the dports/ directory.
>

I just added:

<http://trac.macports.org/browser/contrib/portfile-gen/portfile-gen>

which is a very basic wrapper script around the templates I've used for
years.  It's not much but a place to start, just run it with the port name
and version (and optional port group), redirect into a Portfile and replace
the 'replaceme' bits as needed.  It's written in Tcl so that it should be
easy to integrate into port if it's actually useful.

It currently only handles perl5, python25, and ruby port groups as those are
the only ones I've used.  Feel free to update it if you feel the motivation.

Bryan


> - Jordan
>
> On Oct 30, 2008, at 12:19 PM, Andrea D'Amore wrote:
>
>> Usually I copy a previous portfile or the example from the Guide so  
>> this led me to think if we could have a port named "dummy" or  
>> "portfile-dummy" as file skeleton with all variables, maybe commented.
>> This could speed up new port writing, what do you think?
>