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

Re: ettercap install problems
by Cédric Luthi 25 Jan '07

25 Jan '07

Garrett Reid <garrett.reid(a)gmail.com> on Wednesday, January 24, 2007 at 8:00 PM -0800 wrote: >> For some reason, I'm having issues installing ettercap. It's been >> installed before with a previous darwinports install (but I had to >> remove it, because wireshark wasn't building). Now, with the newest >> darwinports distro from the darwinports website (1.3.2), I ran a >> selfupdate and a sync, and then tried to install ettercap. On 25 janv. 07, at 06:29, Mark Duling wrote: > I don't use ettercap, but it looks like it may be defunct. > > http://ettercap.sourceforge.net/forum/viewtopic.php? > t=2896&sid=4982b342c31d00d7e266936c27a4c8ef Indeed. You may want to use $ sudo port install ettercap-ng instead in order to install ettercap ng 0.7.3 Maybe ettercap port should be removed or aliased to ettercap-ng ? Cédric

1 0

What if software download URL doesn't include version?
by Ryan Schmidt 24 Jan '07

24 Jan '07

I have run into the situation a couple times now that the software developer provides a download URL that does not contain the version number. For example, gtkwave: http://trac.macports.org/projects/macports/ticket/11238 And sitescooper: http://trac.macports.org/projects/macports/ticket/11050 The portfile gets written to download the archive, including its checksums, and then when the author goes and updates the software, it breaks the port because the checksum has changed but the download filename is the same. I don't know about sitescooper, but I've checked with the author of gtkwave, and he cannot provide versioned downloads because he does not have enough webspace to store the prior versions. (The current version is about 2.5 MB.) What should we do in cases like these? Do we go and grab the archives and put them on a MacPorts web server with a versioned URL, or do we use the original download URL and just accept that the port will break when the developer updates the software? Begin forwarded message: > From: Anthony J Bybell > Date: January 24, 2007 00:56:07 CST > To: Ryan Schmidt > Subject: Re: Download specific version of gtkwave? > > Ryan, > > There's no way to download a specific version given that I don't > have the > webspace on my ISP to support all the versions. I will forward out a > tarball of 3.0.14 in my next note. > > -Tony > > > On Tue, 23 Jan 2007, Ryan Schmidt wrote: > >> Hi. Is there a way to download version 3.0.14 -- or any specific >> version -- of gtkwave? All I see on your web page is a way to >> download the "current" version of gtkwave, but for the MacPorts >> project we need a reliable way to download a specific version, even >> after you have released a new version. Thanks.

3 2

Re: [21414] trunk/dports/graphics/gd/Portfile
by Mark Duling 24 Jan '07

24 Jan '07

Port gd2 is at 2.0.33. If gd 1.x is no longer needed couldn't we just delete it and use the gd2 port? Mark macports-dev(a)lists.macosforge.org on Tuesday, January 23, 2007 at 3:36 PM -0800 wrote: >Revision >[ http://trac.macosforge.org/projects/macports/changeset/21414 ]21414 >Author >toby(a)macports.org >Date >2007-01-23 15:36:22 -0800 (Tue, 23 Jan 2007) > >Log Message > >gd 2.0.33 > > >Modified Paths > > [ >fcp://@bubbs.biola.edu,%235000280/MailBox/%23196897907#trunkdportsgraphicsgdPortfile >]trunk/dports/graphics/gd/Portfile > > >Diff > > >Modified: trunk/dports/graphics/gd/Portfile (21413 => 21414) > > >--- trunk/dports/graphics/gd/Portfile 2007-01-23 23:22:13 UTC (rev 21413) >+++ trunk/dports/graphics/gd/Portfile 2007-01-23 23:36:22 UTC (rev 21414) >@@ -2,9 +2,9 @@ > > PortSystem 1.0 > name gd >-version 1.8.4 >-set libver 1.8 >-revision 3 >+version 2.0.33 >+set libver 2.0.0 >+revision 4 > categories graphics > maintainers michaelm(a)opendarwin.org > description GD creates PNG and JPEG images, among other formats >@@ -19,17 +19,11 @@

2 7

Is Apache 2.2.4 healthy?
by Mark Duling 24 Jan '07

24 Jan '07

Ok, so I tried the apxs command on a Mac that has MacPorts Apache 2.2.3 and it works fine. $ /opt/local/apache2/bin/apxs -q CC gcc But on 2.2.4 this happens. $ /opt/local/apache2/bin/apxs -q CC apxs:Error: Sorry, no shared object support for Apache. apxs:Error: available under your platform. Make sure. apxs:Error: the Apache module mod_so is compiled into. apxs:Error: your server binary `/opt/local/apache2/bin/httpd'.. What could be wrong? Mark

2 2

Kernel extensions in MacPorts
by Pierre Queinnec 24 Jan '07

24 Jan '07

Hi all, Eridius pointed me on IRC to MacFUSE, the recently released FUSE port to OS X. I wanted to see if there is interest in having it in our ports. There is a major drawback in having kernel modules in the ports in the fact that it's a tad easier for curious & inexperienced users to mess up their systems. Of course, it's also a lot cooler for some of us to just install sshfs and make it work without spending too much time. This drawback could probably be addressed by having a separate category (something called 'kernel' for example) where we'd warn users that they can mess their systems up if they don't know what they're doing. My first question is wether we want kexts in MacPorts at once. FUSE would be a fine addition then, we could also add something like a tun/tap device. If we are to just distribute the userland stuff, it's going to be harder to get users to update their kexts to match the userland libs versions. Thoughts on this? -- Pierre

5 10

Re: .. perl gurus answer this? - speedycgi
by Mark Duling 23 Jan '07

23 Jan '07

dan(a)frombeantocup.com on Sunday, January 21, 2007 at 10:23 PM -0800 wrote: >Did you ever get CGI-SpeedyCGI to build on OSX? > > >I'm getting the same error you did... Ok, I got it with Jordan's help. Here's what it took changing src/speedy_perl.h -PerlInterpreter *my_perl; +extern PerlInterpreter *my_perl; So I have the port almost ready to go. But the app does an "apxs -q CC" and so it finds Apple's Apache and builds speedycgi for Apple's Apache 1. I symlinked /usr/sbin/apxs to /opt/local/apache2/bin/apxs and now the port chokes because: $ apxs -q CC dyld: Library not loaded: /opt/local/lib/libsqlite3.0.dylib Referenced from: /opt/local/apache2/bin/httpd Reason: image not found apxs:Error: Sorry, no shared object support for Apache. apxs:Error: available under your platform. Make sure. apxs:Error: the Apache module mod_so is compiled into. apxs:Error: your server binary `/opt/local/apache2/bin/httpd'.. What can be done here to support MacPorts Apache 2? Mark

1 0

Naming of postgresql & related
by Jyrki Wahlstedt 23 Jan '07

23 Jan '07

Hi, I just wonder about naming postgresql, some other ports could have the same. Currently postgresql installs v.7.4.12. Then we have postgresql7 (v.7.4.13), postgresql8 (v.8.1.3) and postgresql81 (v. 8.1.4). This is a mess. I think postgresql should always be the latest, then we could, if we want, to have version-specific ports (~7, ~8, ~81). How about this? The related thing comes from the fact that the database formats between point versions of postgresql are not compatible (8.0->8.1). Is there a way to make sure that database is dumped before upgrade. Could one ask a question from the user and wait for an answer (to confirm the operation)? ! ! Jyrki Wahlstedt ! Kolmas linja 12 A 18 mob. +358-400-347 015 skype:jyrkiwahlstedt ! FI-00530 Helsinki http://www.wahlstedt.fi/jyrki/ ! ! Our life is no dream; but it ought to become one and perhaps will. ! PGP key ID: 0x139CC386 fingerprint: F355 B46F 026C B8C1 89C0 A780 6366 EFD9 139C C386

6 7

intltool maintainer is macports-dev@lists.macosforge.org?
by Ryan Schmidt 23 Jan '07

23 Jan '07

What does it mean when a port's maintainer is macports- dev(a)lists.macosforge.org? The intltool port for example. Should that be changed to nomaintainer(a)macosports.org?

3 4

Re: Ticket #11248 commit
by Ryan Schmidt 22 Jan '07

22 Jan '07

On Jan 18, 2007, at 10:16, Cedric Luthi wrote: > On 17 janv. 07, at 21:16, Ryan Schmidt wrote: > >> On Jan 17, 2007, at 11:18, Cédric Luthi wrote: >> >>> Please someone with commit access, take care of this ticket ;-) >>> http://trac.macports.org/projects/macports/ticket/11248 >>> >>> This will be needed for a port I plan to update also: aria2. >> >> Does the current maintainer agree with these changes, and is he ok >> with adding you as a maintainer? > > Actually I don't know. I thought that he was not maintaining > anymore as the 2.6.23 version is dating from 5th January 2006. > > So, the question is officially asked: Michael, do you agree for > this update ? > > Meanwhile, I have added a patch for version 2.6.27 <http:// > trac.macosforge.org/projects/macports/attachment/ticket/11248/ > libxml2-2.6.27_Portfile.patch> that was not present on some > mirrors, plus I removed the gnome mirror as it seems libxml2 no > more stands on gnome mirrors. Cedric, My email to Michael M on January 17 came back today as undelivered. Since Michael is unreachable, I have applied your patch and closed the ticket.

1 0

Re: Can't install libsdl-mixer_fr .. evil inflexible ticketing systems!
by Mark Duling 22 Jan '07

22 Jan '07

Salvatore Domenick Desiano <sal(a)ri.cmu.edu> on Saturday, January 20, 2007 at 12:42 PM -0800 wrote: >SDL is a tricky library because it ties to many, many other libraries, >which makes it more likely to break under different system >configurations than other ports. This isn't an excuse, but an >explanation as to why it may be causing such a headache. It's not >typical. > >According to the bug tracking system, a patch for this problem was >submitted by sethk(a)magnesium.net on 12/23 of last year, but that patch >hasn't been applied and the port isn't maintained. If you can add the >patch to the portfile yourself, you should be in business. Otherwise, >you can see if one of the other MP developers can update the Portfile >for you. This is bug #8771. I'll give the patch a try later and notify the list. Rant: I think people submitting patches should get top priority. It is so difficult to know which bugs are actually fixable in a reasonable length of time. If only there were a "patch in this ticket" flag that users could check these would get committed faster. There are trivial bugs that no one cares about, impossible to fix bugs that no one knows how, and easy ones that already have been fixed (but not committed) all in the same pile. These ticketing systems waste so much of all our time! Mark

1 0