RFE php5: move all graphic libraries into separate variant?

[bulk@…]

Hi,

Just reviewing the tickets for php5, -- looks like you has been busy!

I'm working on a project (actually all of my projects) where I don't need gd and any of the graphics libraries installed ( jpeg, png, freetype, tiff, etc). Locally I made a version where I just ripped them all out and put them into a variant.

But perhaps given their popularity a "no_gd" variant is better?

I'm happy to write up a patch for either -- just let me know which one is better for you, or not.

thanks so much.

--nickg

[ryandesign (Ryan Carsten Schmidt)]

I want gd and the other graphics libraries enabled by default, because many people want to write php scripts that manipulate images. So if anything, we should do a no_gd or no_graphics variant. But what is the advantage of adding such a thing?

[bulk@…]

Hi,

thanks for the quick reply. Yeah, I expect a lot (most?) people might want the graphics on by default. As for a "no_graphics" variant -- I suppose it is a bit mysterious. The short answer is that it saves time and space for our sysadmins/release engineer. They have to frequently nuke /opt/local and rebuild the whole images and not downloading/compiling the graphics libraries saves 15m per cycle.

The long answer is that we are using macports as a development environment. We love MacPorts, but we also need to make a few changes to the ports tree for all sorts of reasons: postgresql82 is required when we want postgresql83, something is out of date, etc. (We are filing bugs/rfes but they take time to clear, etc). Also there are a few bugs, such as python modules or apache randomly breaking on install (known issues). Some package need env variables set before compiling. Instead of making everyone go through the whole port install process, which can take a few hours, we are making a version (or two), tarball all of /opt/local. Then when a new developer comes on board, untar, and 45 seconds later the entire macports is installed, ready to go (with some minor post config). So far it works great -- it's like poor-man's Xen without the kernel ;-) Suggestions/comments welcome.

However to make 'the image', lots of "rm -rf /opt/local; redo.sh" is done. PHP is near the end of the line, and as mentioned, not downloading, not compiling the graphics librarys saves 15m of sometimes time, per cycle. (which can happen many times per day if something screws up, debugging, etc).

Ideally we like to minimize any use of local ports and use as much of the official as possible, hence, our request to have a no-graphics variant. We'll can provide the patch if you want (it's should be simple and harmless).

again, thanks for the speedy reply!

--nickg

[ryandesign (Ryan Carsten Schmidt)]

Sorry for my late reply; I overlooked yours. If you'll supply a patch for a no_graphics variant I can add it to the portfile.

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

Cc Me!

[(none)]

Milestone Port Enhancements deleted

[ryandesign (Ryan Carsten Schmidt)]

Via #19091 practically all variants and default features will be moved to separate ports. gd functions have already been removed and placed in a new port php5-gd.

php5 still declares a dependency on tiff. I can't actually figure out what part of php, if any, actually uses tiff.

[ryandesign (Ryan Carsten Schmidt)]

Replying to ryandesign@…:

php5 still declares a dependency on tiff. I can't actually figure out what part of php, if any, actually uses tiff.

This dependency was removed in r56346. MacPorts php has been fully modular for awhile now.