New port devel/tmake
On Wed, Mar 08, 2000 at 04:47:04PM +0100, Roland Jesse wrote: > >Number: 17265 > >Category: ports > >Synopsis: New port devel/tmake Ha! You beat me to it. I was about to submit mine after a little testing. One of my (new ports/updated ports) needs tmake. > echo x - tmake/pkg/COMMENT > sed 's/^X//' >tmake/pkg/COMMENT << 'END-of-tmake/pkg/COMMENT' > XCreate and maintain makefiles across many platforms and compilers I prefer, Extremely portable perl-based make utility > echo x - tmake/pkg/PLIST > sed 's/^X//' >tmake/pkg/PLIST << 'END-of-tmake/pkg/PLIST' > Xbin/progen > Xbin/tmake What is all this crap below here? We only need freebsd-g++, not all those other OS types. The only useful purpose for a port of tmake would be to generate makefiles from a tmake .pro file. If a developer wishes to distribute other parts of tmake, they can still get the tarball and install it with their own software package. > Xshare/tmake/aix-g++/subdirs.t > Xshare/tmake/aix-g++/app.t > Xshare/tmake/aix-g++/lib.t > Xshare/tmake/aix-g++/tmake.conf [ ... bunch of crap snipped ... ] > Xshare/tmake/freebsd-g++/subdirs.t > Xshare/tmake/freebsd-g++/app.t > Xshare/tmake/freebsd-g++/lib.t > Xshare/tmake/freebsd-g++/tmake.conf Only these are needed, and (I'm not sure) maybe we don't even need the *.t files, but only tmake.conf. > sed 's/^X//' >tmake/Makefile << 'END-of-tmake/Makefile' > X# New ports collection makefile for: tmake > X# Version required: 1.3 > X# Date created: 8 March 2000 > X# Whom: jesse@cs.uni-magdeburg.de > X# > X# $FreeBSD$ > X# > X > XDISTNAME= tmake-1.3 > XCATEGORIES= devel += perl5 > XMASTER_SITES= ftp://ftp.troll.no/freebies/tmake/ > X > XMAINTAINER= jesse@cs.uni-magdeburg.de > X > XNO_BUILD= yes > XWRKSRC= ${WRKDIR}/tmake > XTMAKE_BIN= progen tmake += USE_PERL5= yes > Xdo-install: > X @${MKDIR} ${PREFIX}/share/tmake > X @cd ${WRKSRC}/lib; tar cf - * | (cd ${PREFIX}/share/tmake && tar xf -) > X.for f in ${TMAKE_BIN} > X @${INSTALL_SCRIPT} ${WRKSRC}/bin/$f ${PREFIX}/bin > X.endfor As I said above, this is too much cruft for what will be the 99% case of an install of tmake. -- Will Andrews <andrews@technologist.com> GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y?
Will Andrews <andrews@technologist.com> writes: > One of my (new ports/updated ports) needs tmake. Well, I need it for my own work. :) > > XCreate and maintain makefiles across many platforms and compilers > > I prefer, > Extremely portable perl-based make utility Fine with me. > What is all this crap below here? We only need freebsd-g++, not all those > other OS types. The only useful purpose for a port of tmake would be to > generate makefiles from a tmake .pro file. If a developer wishes to > distribute other parts of tmake, they can still get the tarball and install > it with their own software package. I disagree. It is kind of annoying when ports are only made in a way that they are good as dependencies for other ports but not for serious development besides that. As much as it is necessary to install header files in case of libraries (see math/vtk for a real bad example) it is a good idea to install not only the freebsd-g++ templates for tmake but the couple others that are available, too. > As I said above, this is too much cruft for what will be the 99% case of an > install of tmake. Well, that's the Microsoft argument. ;-) In case my proposal violates common porting practice, do it your way and I will stick with mine on my machine. Roland
Responsible Changed From-To: freebsd-ports->will i'll talk this one up with the originator and close. previously we had a consensus, but i'll followup and close/commit.
State Changed From-To: open->closed committed, thanks!