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

port list inactive output expected?
by jeanpierre＠gmail.com 19 Apr '07

19 Apr '07

hi list - is the output from 'port list inactive' expected? it appears to list the active port version and revision rather than the inactive one. for example: % port list inactive ruby @ 1.8.6 lang/ruby however: % port installed ruby The following ports are currently installed: ruby @1.8.5_2 ruby @1.8.6_0 (active) so instead, now i use: % port installed | egrep -v '(active)' The following ports are currently installed: ruby @1.8.5_2 cheers, jean-pierre

3 4

[11789] upgraded and patched pdflib
by Dominik Fisch 18 Apr '07

18 Apr '07

Hello, I responded to ticket #11789 which indicates that pdflib does not build. I've upgraded pdflib to the current version 7.0.1 (new Portfile) and extended the patch file patch-config-mkcommon.inc.in to solve the described problem. http://trac.macports.org/projects/macports/ticket/11789 Could someone with commit access please review and commit this? Bye Dominik

2 1

g95 and universal option
by Takeshi Enomoto 18 Apr '07

18 Apr '07

Hello I am not with recent discussions these days, but it seems that the universal option is added to g95 as well. A user reported that the build with +universal fails on Intel Mac. I imagine that it would not be easy to build g95 with the universal option. At the momemnt, please remove universal option from g95 package. Ticket #11801. Takeshi

2 1

Portfile authors: pay attention to keywords, eol-style, Id
by Ryan Schmidt 18 Apr '07

18 Apr '07

I have fixed several issues with several portfiles. There was an agreement on the list some months ago that things should be this way, so these commits simply bring noncompliant portfiles back into compliance with the following: - svn:keywords should be set to Id (capital I, lowercase d) http://trac.macosforge.org/projects/macports/changeset/24131 http://trac.macosforge.org/projects/macports/changeset/24132 http://trac.macosforge.org/projects/macports/changeset/24133 http://trac.macosforge.org/projects/macports/changeset/24134 http://trac.macosforge.org/projects/macports/changeset/24135 http://trac.macosforge.org/projects/macports/changeset/24136 http://trac.macosforge.org/projects/macports/changeset/24137 http://trac.macosforge.org/projects/macports/changeset/24138 - svn:eol-style should be set to native http://trac.macosforge.org/projects/macports/changeset/24140 - svn:executable should not be set http://trac.macosforge.org/projects/macports/changeset/24139 - Portfiles should begin with the line "# $Id$" and then a blank line http://trac.macosforge.org/projects/macports/changeset/24131 http://trac.macosforge.org/projects/macports/changeset/24141 http://trac.macosforge.org/projects/macports/changeset/24142 http://trac.macosforge.org/projects/macports/changeset/24143 To ensure that the correct properties automatically get set on your new Portfiles, you can edit your ~/.subversion/config file, turn auto- props on, and add this auto-prop definition: Portfile = svn:eol-style=native;svn:keywords=Id For consistency and conformance with the Subversion documentation let's please use Id, not id, for the keyword name. This recommendation should probably be in the documentation somewhere but I haven't looked yet where it might best be included. If someone else would add this to the wiki, or even just point out where in the wiki it should go, that would be appreciated. I once said I would work on a pre-commit hook script we could install which would reject any commit that did not conform with these requirements. I haven't gotten around to that yet, but I haven't forgotten either.

5 6

Re: freeimage # -*- tcl -*-
by Emory Smith 18 Apr '07

18 Apr '07

On Apr 17, 2007, at 3:45 PM, macports-dev- request(a)lists.macosforge.org wrote: > Date: Tue, 17 Apr 2007 22:02:54 +0200 > From: Jochem Huhmann <joh(a)gmx.net> > > On 2007-04-17, at 12:44, Ryan Schmidt wrote: > >> The portfile for freeimage begins with this line: >> >> # -*- tcl -*- >> >> I don't know what the line does. I guess it informs some editor >> that this is a tcl file, but I don't know what editor that would >> be. Does anyone know? > > It's Emacs. > >> No other portfiles begin with (or contain) such a line, so I would >> like to remove it for consistency (so that all portfiles begin with >> the # $Id$ line). Any objection to removing this line? > > Is there any technical merit to consistency here? If not and if you > absolutely *have* to do something, replace it for clarity with > > # Emacs, this is a -*- tcl -*- file. > > or something like that. > > Jochem as an alternative, adding the following to your .emacs will tell emacs to use tcl mode for anything with a filename of "Portfile". (add-to-list 'auto-mode-alist '("Portfile$" . tcl-mode)) note however that once you do this, any microsoft word documents saved as "Portfile" and subsequently opened in emacs will be opened in tcl-mode. -emory

1 0

Announcing MacPorts release 1.4.3
by James Berry 18 Apr '07

18 Apr '07

The MacPorts team is very proud to announce our third release of MacPorts within several days. The pace of change has been fast and furious. This time we're just furious: Release 1.4.3 (17-Apr-2007): - Fix bug in launchd support, introduced in 1.4.2. Remove remnants of launchd enable flag which caused reversion to systemstarter in 1.4.2. (jberry r24151). - add functions 'backup' and 'lipo' along with some description to be used for lipo-based universal variants, tested with openssl. These functions should be considered test only for the time being, and should not yet be adopted widely by port authors. (pipping r24148). If you installed ports with 1.4.2 that have startup items, they were installed with SystemStarter, rather than Launchd support. You'll want to rebuild and reinstall those ports. We (singular) apologize for this issue. James

1 0

freeimage # -*- tcl -*-
by Ryan Schmidt 17 Apr '07

17 Apr '07

The portfile for freeimage begins with this line: # -*- tcl -*- I don't know what the line does. I guess it informs some editor that this is a tcl file, but I don't know what editor that would be. Does anyone know? No other portfiles begin with (or contain) such a line, so I would like to remove it for consistency (so that all portfiles begin with the # $Id$ line). Any objection to removing this line?

2 1

Change in ports.conf and ~/.portsrc search paths
by James Berry 17 Apr '07

17 Apr '07

I checked in yesterday a change the search path for ports.conf. Previously, the first of the following files found was used as the configuration file for MacPorts: - File identified by the environment variable PORTSRC - File at ~/.portsrc - File at ${prefix}/etc/ports/ports.conf I've changed this behavior. The search path is now: - File identified by the environment variable PORTSRC - File at ~/.macports/ports.conf - File at ${prefix}/etc/ports/ports.conf In other words, if you have a file at ~/.portsrc, you should move it to ~/.macports/ports.conf. I have a feeling this affects ~0 people. Please let me know if you have any comments about this change. James

3 6

GSoC work and svn
by Juan Manuel Palacios 17 Apr '07

17 Apr '07

Hey GSoC mentors! Before GSoC students with our project start committing their work into our repo, I wanted to suggest some organizational guidelines to streamline the workflow and also secure trunk from breaking with potentially experimental code. Namely, I was thinking maybe we should create either a single GSoC dedicated branch, and appropriate subdirectories therein for each of our students (e.g. /branches/GSoC2007/pipping_universal), or separate, well defined branches for each (e.g. /branches/GSoC2007_pipping_universal), depending on consensus. In any case, I believe we should keep GSoC produced code out of trunk until projects are called completed, both to secure trunk from breaking but also for accountability of the project and the student's progress (if everything goes into trunk it becomes easy to mix things up). If we go this route, which I strongly recommend, students would, of course, have to handle keeping their branches in sync with trunk when appropriate, so that merging back into trunk upon project completion is as painless as possible. Thoughts? -jmpp PS: Elias already made a commit to base from his GSoC work, r24148, so he would have to back that one out and commit it to his branch (or sub-branch). PPS: Someone (Paul?) please make sure Eugene Pimenov gets involved in this discussion, I couldn't find any mailing information for him anywhere (actually, he should be required to sing up to this list and to mp-changes if he's going to be committing to our repo, I couldn't find him on either list's rooster).

1 0

enhancement of elvis' Portfile
by Emmanuel Hainry 17 Apr '07

17 Apr '07

Hi all, I have recently modified elvis (vi clone) portfile so that it correctly destroots (was installing files out of ${destroot} and even in /etc). It now works for me. Could someone check and hopefully commit? Emmanuel

2 3