As we near the 9 month anniversary of this, [er [EMAIL PROTECTED], I recommend that we commit the new version of this port.
~BAS On Fri, 2008-05-30 at 17:11 -0400, Brian A. Seklecki wrote: > All: > > Normally I would say that this PR may be approaching the point where we > override the maintainer -- the problem is that I haven't received any > feedback from anyone other than my development team. > > ~BAS > > On Mon, 2008-04-07 at 11:32 -0400, Brian A. Seklecki wrote: > > The associated PRs are: > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/122450 > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/121791 > > > > My draft version of the rewrite is at: > > > > http://people.collaborativefusion.com/~seklecki/phing-2.3.0-CFI1.tar > > > > I would note that there is a 20-line count diff of the file-contents > > listing -- someone should dig through it to validate that some files > > massive list of files has not been added since I originally composed the > > PLIST back in .... late October of 2007? I just never filed PR for some > > reason. > > > > Feedback appreciated -- be sure to CC: [EMAIL PROTECTED] with > > title "e: ports/122450: devel/php5-phing redesign" > > > > TIA, > > > > ~BAS > > > > On Fri, 2008-04-04 at 12:43 -0400, Brian A. Seklecki wrote: > > > I remember now why I never filed the PR -- the whole thing is fucked. I > > > realized that after I tried to conver the FreeBSD port from a simple > > > do-install: target to use ${PORTSDIR}/devel/pear/bsd.pear.mk: > > > > > > > > > Here are the two big issues that I require guidance with: > > > > > > 1) FreeBSD Ports PEAR subsystem designates pear package contents as > > > either: $TESTS $SCRIPTFILES $SQLS $EXAMPLES $DOCS or $FILES > > > > > > Not the most ambiguous designations ever, but close. > > > > > > Pear packages use categories: "script", "php", "data", "doc" > > > > > > Could anyone comment on the mappings? > > > > > > 2) The PEAR port is installing a "script" in $PREFIX/bin/phing > > > as a bourne shell script wrapper around $PREFIX/share/pear/phing.php > > > > > > script /usr/local/bin/phing > > > > > > > > > $ ident /usr/local/bin/phing > > > /usr/local/bin/phing: > > > $Id: pear-phing 123 2006-09-14 20:19:08Z mrook $ > > > > > > Where as we are running some sed(1) statements on: > > > > > > ${WRKSRC}/bin/phing the installing it as ${PREFIX}/bin/phing > > > > > > However, i think some of these post-extract: targets are legacy > > > because one substrpl is: "s|/opt/phing|${PREFIX}/lib/php/phing|" > > > > > > But: > > > > > > $ grep -i opt \ > > > [../obj]/devel/php5-phing-work/work/phing-2.3.0/bin/phing.php > > > // Set any INI options for PHP > > > > > > No such instances of this string exist any more in "phing.php" or > > > "phing" in 2.3.0x > > > > > > I'm filing the PR now and I'll let everyone else fight over the proper > > > solution. > > > > > > ~BAS > > > > > > > > > On Fri, 2008-04-04 at 11:46 -0400, Brian A. Seklecki wrote: > > > > > > > > > > > > On Fri, 2008-04-04 at 11:27 -0400, Brian A. Seklecki wrote: > > > > > Michiel et. al.: > > > > > > > > > > Some of my developers are telling me that they are having some > > > > > trouble > > > > > using the stable v2.3.0 in FreeBSD ports. > > > > > > > > Oh yea, my day is done for: > > > > > > > > [EMAIL PROTECTED]:/home/seklecki$ wc -l phing_port.txt phing_pear.txt > > > > 272 phing_port > > > > 301 phing_pear > > > > > > > > 573 total > > > > > > > > I have a vague recollection, maybe 6 months ago, converting the FreeBSD > > > > port to use the PEAR-framework so that it is properly registered -- > > > > spending 18 hours sorting out PLIST differences. > > > > > > > > What happened? Maybe I forgot to file PR? > > > > > > > > ~BAS > > > > > > > > > > > > > I'm digging for details now -- but I may be related to the path in > > > > > which > > > > > the PEAR package installs files v.s. the Port. > > > > > > > > > > Any insight into this before I burn my day down? > > > > > > > > > > ~BAS > > > > > > > > > > On Sun, 7 Oct 2007, Michiel Rook wrote: > > > > > > > > > > > Hi Brian, > > > > > > > > > > > >> We should endeavor to update this to something recent. We'll try > > > > > >> this from > > > > > >> here and forward results on. > > > > > > > > > > > > That'd be great! The latest release is 2.3.0RC1 - we're hoping to > > > > > > release > > > > > > 2.3.0 soon(ish). > > > > > > > > > > > > regards, > > > > > > > > > > > > Michiel > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > l8* > > > > > -lava (Brian A. Seklecki - Pittsburgh, PA, USA) > > > > > http://www.spiritual-machines.org/ > > > > > > > > > > "Guilty? Yeah. But he knows it. I mean, you're guilty. > > > > > You just don't know it. So who's really in jail?" > > > > > ~Maynard James Keenan > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
