L-Breeder is a program which allows you to display, breed, and genetically engineer L-system forms. WWW: http://pixie.oum.ox.ac.uk/L-Breeder/ - David dyeske@yahoo.com Fix: http://pigseye.kennesaw.edu/~dyeske/freebsd/L-Breeder.shar
Responsible Changed From-To: freebsd-ports->lioux I'll handle this
Hi, I made a few changes to the port mostly having to do with port rules. 1) Port HAS to respect {CC,CXX,CFLAGS}. Check post-patch target http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/x3031.html applies to CC,CXX as well. I am updating the porters handbook on this. These were done as port-patch regexp expressions because they preferred over file patches for 2 main reasons: i) easier to maintain across port updates ii) easier on the repo since it one less file to keep track of Of course, we still use file patches if the regexp will be too complicated. Added USE_REINPLACE= yes to port due to need of a regexp command. Using PERL is deprecated. Assume a SED regexp when using USE_REINPLACE_CMD. 2) Also, remove -O2 unless WITH_OPTIMIZED_CFLAGS is defined because this breaks ALPHA ARCH for example. Also, we should try to comply to system CFLAGS instead of rolling our own whenever we can. Furthermore, it is a user tweakable option so nothing was lost (check pre-everything target) 3) Prefixed elements in do-install target with @. We should decrease the noise if we can. That was not useful information so echo_off is better 4) Renamed patches under files/ according to port conventions - patch-Makefile -> patch-LBreeder::Makefile - patch-MyTextFrame.cpp -> patch-LBreeder::MyTextFrame.cpp - patch-aa -> patch-GL_Lsystem::Makefile 5) Simplified patch-LBreeder::Makefile so that it benefitted from GTK_CONFIG variable. To use that I had to add USE_GNOMENG= yes USE_GNOME= gtk12 to ports' Makefile 6) Fixed a small grammar error in pkg-descr 7) Added "et al" to end of Whom header line in ports' Makefile since there are quite a few changes. This is pretty much it. One last issue. Lower case is preferred in port dir names. However, PORTNAME can still contain upper case. This is a tradition more than a rule. Nonetheless, this was passed to me from my mentor so I am doing the same. Check audio/xnap for an example. What would happen? 1) port dir would be l-prefix 2) portname would be L-PREFIX Simple as that. Let me know what do you think. Although, most of the changes were due to ports' rules, we can try discussing them. After all, this is your port. Regards, -- Mario S F Ferreira - DF - Brazil - "I guess this is a signature." Computer Science Undergraduate | FreeBSD Committer | CS Developer flames to beloved devnull@someotherworldbeloworabove.org feature, n: a documented bug | bug, n: an undocumented feature
State Changed From-To: open->closed Committed, thanks!