On Sep 18, 2013, at 05:04, Joël Brogniart wrote: > Excuse me if that's a recurrent question, but I'd like to know what is the > best way or practice to submit a port.
File a ticket in the issue tracker. > More precisely, some time ago I made a submission with ticket number 37754 (a > port for CPAN PERL module Role::Tiny). Ah, you've already filed a ticket, and we haven't noticed. Sorry about that. Sometimes tickets fall through the cracks. When that happens, just send a message to macports-dev reminding someone to take a look at it. > And some more submissions at that time. As I was (and still am) a newby, my > submissions needed some adjustments. Later, the original tool evolved and I > replaced the portfile in the same ticket. Now, a new version of the CPAN > module is available and if I succed to install the new version on my local > repository, I'll could update the portfile. The status of the port is "new". > > With the new portfile, should I: > - add a patch to the initial portfile in the same ticket, > - replace the old portfile with the new portfile in the same ticket, > - add the new portfile in the same ticket (the ticket will have different > portfile version), > - create a new ticket for the new portfile, > - wait until the original ticket is accepted and then propose a patch for > port ? Since the port has not been committed yet, you can just add a new portfile to the existing ticket. Replacing the old portfile is fine. Had the port already been committed and the ticket closed, we would want a new ticket and a unified diff of your changes. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
