Re: [Patch] <rename> recipe step (also: suggested additional recipe steps)

On 24 June 2012 08:49, Tim Cuthbertson <tim <at> gfxmonk.net> wrote:
> Hi all,
>
> I'd like to add some additional <recipe> step types, because it's
> getting annoying to have to re-host archives or even overlays of other
> people's software for simple changes.
>
> Node.js software in particular is annoying, as every library seems to
> call their module "index.js" and use the indirection of `npm` (the
> node package manager) to turn this into something usable at install
> time. Why they choose to do this baffles me, and my attempts to
> encourage an archive layout that actually works with the runtime
> they're targeting have been woefully unsuccessful so far[1].
>
> https://github.com/substack/js-traverse/pull/24
>
> So anyway, I've added a <rename src="source" dest="dest"/> step in the
> attached patch. If it's OK, I'd like to go ahead and also add some
> more shortly:
>
>  - <remove path="unwanted/dir"/> (mostly just for saving disk space)
>  - <add-directory path="dir"/> (likely used in conjunction with "move")
>  - <add-container-dir name="toplevel"/> (this moves all current
> contents in the implementation inside the newly-created toplevel
> directory, which I think is a more general solution to packaging
> node.js libs)
>
> If I can, I'd like to resurrect my <patch/> recipe step as well. That
> will be a bigger one.
>