January 2008 - macports-dev - lists.macosforge.org

Re: [33003] trunk/dports/lang
by Ryan Schmidt 17 Jan '08

17 Jan '08

On Jan 16, 2008, at 10:09, reiffert(a)macports.org wrote: > +configure {} You should use "use_configure no" instead of "configure {}". You may also want "universal_variant no" or provide another solution for universal building.

2 1

32937] trunk/dports/gnome/evince/Portfile
by Guido Soranzio 17 Jan '08

17 Jan '08

Randall Wood wrote: > You might want to note that for the GNOME project, packages > with a version x.y.z where y is an odd number are normally > considered unstable, not fit for daily use. When I submitted the patch to make djvulibre compile again by adding the -dylib_file option to the linker (as recently suggested by Apple QA1567 for all the programs using OpenGL), I noticed that in evince 2.11.1 the support for this format is active by default and it was very simple to add a "djvu" variant by simply requiring the presence of djvulibre in the system, I am not having the problem in compiling evince as reported by other users and, yes, I know that the Gnome 2.(2*n)+1.z releases are in preparation for the upcoming 2.2*(n+1).0 stable release but, looking at the changelog of evince, it seemed that their release process is quite different from the rest of the Gnome libraries and that a lot of bugs were fixed. There are more, much more serious problems in Gnome at the moment: until my latest patches to PyGTK, I couldn't even compile it under Leopard and running it is still a painful experience. I am noticing small improvements with every new release candidate that the Xquartz team is lately releasing but many broken things are still to be restored. Thanks to my workaround to another issue regarding missing symbols, now I am able to run Nautilus for the fist time. Gnome-control-center, which was providing the Nautilus extensions with the missing symbols, is still far from be working correctly in Leopard and probably will never be.

1 0

Changes for 1.6.1
by Juan Manuel Palacios 17 Jan '08

17 Jan '08

Hello everyone! As you may have seen, I started getting the release_1_6 branch in sync with trunk in a couple of recent commits, in preparation for the 1.6.1 release. They're almost in sync, except for the following: Outstanding changes: *) Anders: r32722 and r32801, enabling and disabling cURL's --remote- time: so, I gather we're just as if r32722 (addition of --remote- time) had never gone in, yes/no? any word on the development of this feature? should I schedule it for 1.6.1? keep in trunk for the time being, instead? *) Markus: r31954, r32194, "merge" function for universal building (and r32500 and r32501, Ryan's related typo fixes): last I read on this list, there were concerns about changing the platforms for which we build universal, with respect to universal binaries that were built for the previous set of platforms. Any advise on what should be done? Are we good to go releasing this code to the public? Or should we instead keep it in the oven a bit longer? Blocked changes: *) James: all changes related to the addition of MacPorts paths to / etc/paths.d and /etc/manpaths.d (r31491, r31492, r31495, r31496, r31520, r31600, r31946), as we're still using the postflight script (much improved this time round, thankfully! -- I've received quite some good feedback this time round). So... anything else I might be missing? Now is the time to chime in ;-) I'll be posting an rc for 1.6.1 as soon as I get a chance. Regards,... -jmpp

2 1

Re: Creating portfile for program that includes StartupItems
by markd＠macports.org 16 Jan '08

16 Jan '08

>Date: Wed, 16 Jan 2008 01:36:19 +0000 (UTC) >From: Brooks Clark <mbrooksclark(a)mac.com> >Subject: Creating portfile for program that includes StartupItems > script >To: macports-dev(a)lists.macosforge.org >Message-ID: <loom.20080116T012145-937(a)post.gmane.org> >Content-Type: text/plain; charset=us-ascii > >I'm trying to put together a portfile for some software that already >compiles >and runs on a Mac. I'd like to make the installation a bit easier, though, >by creating a port, especially since the software already has several >MacPorts dependencies. The software is actually a set of about six or so >daemons that should be run at startup time. > >The source code ships with a working StartupItems script. > >I've gotten the portfile to the point where it downloads the source, >compiles, and installs the executbles. I'm not having much luck with >the startup script, however. > >Can anyone point me to any examples of portfiles that I could use >as a go-by for launching multiple daemons at startup? Is it possible >(preferred?) to just use the StartupItems script that comes with the >software? Any recommendations or suggestions for how to best install >the startup items would be much appreciated. Hi Brooks, It is fine to use the startupitems script that come with a port if it works ok on OS X, and if the developer considers the script adequate you don't need to reinvent the wheel. On the other hand, if the developer provided scripts is very simple and merely launches daemon(s) and nothing more, there is not a lot of reason to use it and by using MacPorts startupitems to launch the daemon directly (startupitem.executable) where possible you'll get the monitored daemon that will be restarted if it dies. If you have a port that uses multiple daemons and a startup script is provided, it might be the best to use the script provided. But if the script merely launches a bunch of daemons then you could provide multiple startup scripts using MacPorts. But for more than one startup script per port, you'll end up creating some .plist files and copying them manually since only one startupitem per port can be supported automatically. See the net/nedi port for how I supported 3 startupitems for a port. See net/zabbix for an example of a startupitem that uses a distro provided startup script. BTW, one thing not supported is inetdcompatibility for daemons, though this is not needed frequently. That requires creating a .plist manually and copying it during the port install also. Mark

1 0

Re: Subject: [32751] net/dhcp startupitem
by markd＠macports.org 16 Jan '08

16 Jan '08

>i Mark, > >So it looks like the bit magic that got this to work is the -f >command, which basically tells dhcpd not to daemonize, which would be >a good thing in our case, as the process of daemonizing would look to >daemondo or launchd as if dhcpd were exiting, which would cause the >constantly restarting behavior Blair described. > Hi James, So I've looked up what "daemonize" means and I see it entails making a child of the initializing process. So I understand why daemondo thinks a daemonized process has exited. But might some processes not have a switch to keep in the foreground as in the case of dhcp? And if not, would that be the rare case where startupitem.pidfile would be used with startupitem.executable? If I recall correctly, they could be used together but I hadn't thought of a reason where it would be useful to do so. At the very least I should document that processes that daemonize are a problem for startupitem.executable. Mark

2 1

Re: [32983] trunk/dports/gnome/libgtkhtml3/Portfile
by Juan Manuel Palacios 16 Jan '08

16 Jan '08

On Jan 15, 2008, at 8:23 PM, nox(a)macports.org wrote: > Revision > 32983 > Author > nox(a)macports.org > Date > 2008-01-15 16:53:06 -0800 (Tue, 15 Jan 2008) > Log Message > > libgtkhtml3: > * Fixed dependencies. > * Removed useless configure env variable. > Modified Paths > > trunk/dports/gnome/libgtkhtml3/Portfile > Diff > > Modified: trunk/dports/gnome/libgtkhtml3/Portfile (32982 => 32983) > --- trunk/dports/gnome/libgtkhtml3/Portfile 2008-01-15 23:56:28 UTC > (rev 32982) > +++ trunk/dports/gnome/libgtkhtml3/Portfile 2008-01-16 00:53:06 UTC > (rev 32983) > @@ -2,10 +2,11 @@ > > PortSystem 1.0 > > -name libgtkhtml3 > +name libgtkhtml3 > set my_name gtkhtml > version 3.16.0 > set branch [join [lrange [split ${version} .] 0 1] .] > +set revision 1 > Off the top of my head, I'd be wary this local "revision" variable may collide with the internal "revision" property of Portfiles. I don't see any other use of "revision" in your Portfile which makes me think that you are using it in the regular context of a Portfile revision; but if that's the case, why do you use "set"? Regards,... -jmpp

2 1

Re: [32937] trunk/dports/gnome/evince/Portfile
by Randall Wood 16 Jan '08

16 Jan '08

You might want to note that for the GNOME project, packages with a version x.y.z where y is an odd number are normally considered unstable, not fit for daily use. On 15 Jan 2008, at 06:07, gui_dos(a)macports.org wrote: > Revision32937Authorgui_dos(a)macports.orgDate2008-01-15 03:07:18 -0800 > (Tue, 15 Jan 2008)Log Message > Update to evince 2.21.1 > Added "djvu" variant > Modified Paths > • trunk/dports/gnome/evince/Portfile > Diff > Modified: trunk/dports/gnome/evince/Portfile (32936 => 32937) > --- trunk/dports/gnome/evince/Portfile 2008-01-15 10:38:53 UTC (rev > 32936) > +++ trunk/dports/gnome/evince/Portfile 2008-01-15 11:07:18 UTC (rev > 32937) > @@ -1,7 +1,7 @@ > # $Id$ > PortSystem 1.0 > name evince > -version 2.20.1 > +version 2.21.1 > description Evince is a document viewer for multiple document > formats like pdf, and many others. > long_description ${description} > maintainers nomaintainer > @@ -10,7 +10,7 @@ > homepage http://www.gnome.org/ > master_sites gnome:sources/evince/[strsed ${version} {/\.[0-9]* > $//}]/ > use_bzip2 yes > -checksums md5 c0f3e4d5279ef3d08cc46b752e230c01 > +checksums md5 24fb73444987357373098e57c8361ebb > depends_lib \ > port:atk \ > port:audiofile \ > @@ -29,6 +29,7 @@ > port:gnome-icon-theme \ > port:gnome-vfs \ > port:gtk2 \ > + port:hicolor-icon-theme \ > port:jpeg \ > port:libart_lgpl \ > port:libglade2 \ > @@ -52,6 +53,11 @@ > port:perl5.8 \ > port:pkgconfig \ > port:scrollkeeper > + > +variant djvu { > + depends_lib-append port:djvulibre > +} > + > configure.args \ > --disable-scrollkeeper \ > --enable-nautilus \ > _______________________________________________ > macports-changes mailing list > macports-changes(a)lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-changes Randall Wood randall.h.wood(a)alexandriasoftware.com http://shyramblings.blogspot.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy."

1 0

Creating portfile for program that includes StartupItems script
by Brooks Clark 16 Jan '08

16 Jan '08

I'm trying to put together a portfile for some software that already compiles and runs on a Mac. I'd like to make the installation a bit easier, though, by creating a port, especially since the software already has several MacPorts dependencies. The software is actually a set of about six or so daemons that should be run at startup time. The source code ships with a working StartupItems script. I've gotten the portfile to the point where it downloads the source, compiles, and installs the executbles. I'm not having much luck with the startup script, however. Can anyone point me to any examples of portfiles that I could use as a go-by for launching multiple daemons at startup? Is it possible (preferred?) to just use the StartupItems script that comes with the software? Any recommendations or suggestions for how to best install the startup items would be much appreciated. Thanks, Brooks

1 0

Abdon qca-tls?
by Rolf Würdemann 16 Jan '08

16 Jan '08

Hi everybody ... during the transfer of qca 1.0.0 to qca 2.0.0 qca-tls is no longer part of qca (TLS is now done by qca-ossl) - and was only needed by the 0.9.3 version of psi (which is now changed to 0.11) should I simply drop the port - or better leave some message for a while and drop then? Hints? Comments? Reg's, Rolf -- Security is an illusion - Datasecurity twice Rolf Würdemann - private: rowue(a)digitalis.org - office: rowue(a)crew-gmbh.de GnuPG fingerprint: 7383 348F 67D1 CD27 C90F DDD0 86A3 31B6 67F0 D02F jabber: rowue(a)digitalis.org 2F66A061 89BCA1A0 AD654827 6FD037FF 53C3E932

1 0

(Mass) Update for gtkglext on leopard?
by Rolf Würdemann 16 Jan '08

16 Jan '08

Hi everybody .... as you (perhaps) now, there is a linking problem with gtkglext on leopard that is fixed (#13624) ... the maintainer doesn't react, so I would send him an email and wait 72 hours before commiting the update. (after sign in for commiter is done) but all applications using gtkglxt have to get updated too (#13737) Soo - what should I do? Wait for all maintainers (if avail) to change the portfiles? - Do an automatic mass update? (Some shell script which appends the portfiles and commits them (one by one))? Write all maintainers to change their portfiles? The documentation state this problem as an exception to the rules of changing only one file per time/wait for the maintainers... what is your opinion/recommandation? Reg's Rolf -- Security is an illusion - Datasecurity twice Rolf Würdemann - private: rowue(a)digitalis.org - office: rowue(a)crew-gmbh.de GnuPG fingerprint: 7383 348F 67D1 CD27 C90F DDD0 86A3 31B6 67F0 D02F jabber: rowue(a)digitalis.org 2F66A061 89BCA1A0 AD654827 6FD037FF 53C3E932

2 2