On Mon, May 23, 2011 at 11:10 AM, Parrot <[email protected]> wrote: > #1290: Produce Single PBC from Multiple PIR Files with -o > -----------------------+---------------------------------------------------- > Reporter: chromatic | Owner: > Type: feature | Status: new > Priority: normal | Milestone: > Component: core | Version: > Severity: medium | Keywords: > Lang: | Patch: > Platform: | > -----------------------+---------------------------------------------------- > > Comment(by whiteknight): > > We would need to rework the command-line parsing logic to handle multiple > input files if the -o option were used (I suspect listing multiple input > files without -o should be treated as an error because it's nonsensical). > We would need to compile each, merge each one into a single master > packfile, and then output that packfile to file. With the new embedding > API and some of the IMCC/Packfile changes recently, this actually should > not be too hard of a project. > > The question is whether we want to do this with pbc_merge available. And, > if so, do we want to keep pbc_merge or deprecate that?
FYI, pbc_merge merges already-generated PBC files, which is different than the request on this ticket (to generate a single PBC from multiple PIR files.) As long as the functionality is still there, I don't care which way I have to invoke it (barring normal deprecation issues.) -- Will "Coke" Coleda _______________________________________________ parrot-tickets mailing list [email protected] http://lists.parrot.org/mailman/listinfo/parrot-tickets
