[133725] trunk/dports/_resources/port1.0/group/octave-1.0.tcl

[Michael Dickens]

Yes, that's true: I can have any number, and they are executed in the
order declared. The Octave PortGroup's post-patch would always be
declared first, and it (1) creates a tarball of the current worksrcpath,
then (2) deletes the worksrcpath since it is not used by the Octave pkg
installer. So, if I want to reinplace during a post-patch, I can't.
Combining the PortGroup's post-patch and pre-configure into the latter
allows for actual file manipulation during Portfile post-patch, which is
a good thing; wish I had done it this way when I wrote the original
code, but better late than later. - MLD

On Mon, Mar 9, 2015, at 01:03 PM, Ryan Schmidt wrote:
> In case you're thinking that by using a post-patch block in a portgroup,
> that means you can't have a post-patch block in a portfile, that's not
> so. There's no problem with having any number of pre- or post-phase
> blocks, in portgroups or portfiles. They all get run (currently: in the
> order in which they're declared).