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

Ticket #14569: update pv
by Matthew K. Meissner 08 Mar '08

08 Mar '08

Hi, Would a committer mind taking a look at ticket #14569 and committing it if deemed OK? I submitted the ticket on Thursday and had a user of the port inquire today on the status. Thanks, Matt -- Matt Meissner meissnem at gmail.com

2 1

Re: RFC: MacPorts Filesystem Hierarchy Standard
by markd＠macports.org 08 Mar '08

08 Mar '08

>> > I wrote the Filename hierarchy standard for MacPorts. >> > I know there's already porthier(7), but I thought it would be nice >> > to have more specific standard. >> >> So is this meant to replace porthier(7)? Than you should write it up as >> a patch for the manual page. I don't think we need yet another place >for >> it. Coordinate with markd and simon on this. > >No, I meant to replace hier part of the Guide. >After this change, porthier change would be followed. > >> > This document defines the standard placement of file and directory >> > installed by MacPorts. This document also intended to replace the >> > existing porthier(7)[1]. Every ports in MacPorts project should >follow >> > this standard. Most of this based on hier(7)[2]. The hier part of the guide is meant to provide the source for the porthier.7 man page. It doesn't right now, but we are intending to base all manpages on the guide very shortly, so changing the guide is how to get the man pages changed. Right now the guide has the most up-to-date information because of this pending new way. > I'm not really qualified to comment on the technical merits of your proposal. But I'd be happy to look over what you've written for style and format if it passes approval by our base developers. Mark

4 4

py-twistedweb2 and py25-twisted-web2 uses different name convension
by js 08 Mar '08

08 Mar '08

Hi, I noticed that twisted for python2.4 and 2.5 uses different name convension. I opened new ticket http://trac.macosforge.org/projects/macports/ticket/14375 Shouldn' they use the same convension?

3 6

Re: Pre-commit script to reject commits
by markd＠macports.org 07 Mar '08

07 Mar '08

>> Thanks for the clarification, I think you are kind of right. But it >> will >> always hit someone not affected by the update. For example, changing >> depends_* inside some variants and incrementing the revsion forces all >> users to recompile - even if they don't use this variant... > >And yet, incrementing the revision is the correct thing to do, if >doing so will fix the install for even just a few users, even at the >risk of unnecessarily rebuilding the port for others. For example, >perl5.8 was updated from revision 1 to 2 in r34508. As I understand >it, the change was irrelevant for those using gcc 4.0 (i.e. at least >all Mac users), but was necessary for those using gcc 4.2 (perhaps >Linux or FreeBSD users). Oh well. I don't think we're all have the same understanding of when the port revision number should be incremented. If there are guidelines we could all agree to it could be documented, and (along with some nagging) we'd probably see a lot less variance, not that automation wouldn't be fine too. Mark

1 0

Pre-commit script to reject commits
by Blair Zajac 07 Mar '08

07 Mar '08

I was thinking that we should have a pre-commit script reject commits if a portfile does not increment a revision or version if it changes any of its depends_*. I find this pretty annoying to see commits that add a dependency that don't bump a version or revision. Any other things we should reject commits on? Blair

3 4

Fwd: [MacPorts] #14342: python25 drops modules by default, but python25 doesn't
by js 07 Mar '08

07 Mar '08

# Moving from Trac ticket #14342 > No, py25-foo can have different dependencies than py-foo. I don't know > what you wanted to tell us with this. I meant if we would change python24 to drop some standard modules like the current python25 port does, py-foo and py25-foo's dependencies would be the same. Not sure this is 100% same but almost the same I assume. > And there is no problem that we have more py-* ports than py25-* ports. We > just add what people request. If nobody needs a port, but it is in the > tree, it is just more work for maintainers. So if you need some port, ask > for it. No problem, but Python project now recommend users to use python2.5, not 2.4. Providing a lot of ports to python25 users would encourage users to use python2.5. Some people don't bother to write reports even if they want. I like to add more py25- ports to make python25 looks more *atrractive*. Forwarded Conversation Subject: [MacPorts] #14342: python25 drops modules by default, but python25 doesn't ------------------------ From: MacPorts <trac(a)macosforge.org> Reply-To: noreply(a)macosforge.org To: ebgssth(a)gmail.com, macports-tickets(a)lists.macosforge.org Cc: mww(a)macports.org Date: Sat, Feb 16, 2008 at 11:51 AM #14342: python25 drops modules by default, but python25 doesn't -------------------------------+-------------------------------------------- Reporter: ebgssth(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Keywords: python | -------------------------------+-------------------------------------------- Python2.5 disables common modules by default, but python2.4 doesn't. See dports/lang/python25/files/patch-setup.py {{{ # This global variable is used to hold the list of modules to be disabled. -disabled_module_list = [] +disabled_module_list = ["zlib","_hashlib","_ssl","_bsddb","_sqlite3","_tkinter","bz2","gdbm","readline","_curses","_curses_panel"] }}} IMHO, all python pors should be as similar as they can be. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14342> MacPorts </projects/macports> Ports system for Mac OS -------- From: MacPorts <trac(a)macosforge.org> Reply-To: noreply(a)macosforge.org To: ebgssth(a)gmail.com, macports-tickets(a)lists.macosforge.org Cc: mww(a)macports.org Date: Sat, Feb 16, 2008 at 11:52 AM #14342: python25 drops modules by default, but python25 doesn't --------------------------------+------------------------------------------- Reporter: ebgssth(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Resolution: | Keywords: python --------------------------------+------------------------------------------- Comment (by ebgssth(a)gmail.com) If there's a reason, please make it clear by leaving comments about that on the patch file. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14342#comment:1> [Quoted text hidden] -------- From: MacPorts <trac(a)macosforge.org> Reply-To: noreply(a)macosforge.org To: ebgssth(a)gmail.com, macports-tickets(a)lists.macosforge.org Cc: mww(a)macports.org Date: Sat, Feb 16, 2008 at 12:02 PM #14342: python25 drops modules by default, but python25 doesn't --------------------------------+------------------------------------------- Reporter: ebgssth(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Resolution: | Keywords: python --------------------------------+------------------------------------------- Comment (by raimue(a)macports.org) These are provided as seperate ports. For example py25-hashlib, py25-zlib and others. I don't know what the advantage of that was, but we already had that discussion once. Portfile writers should include correct dependencies. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14342#comment:2> [Quoted text hidden] -------- From: MacPorts <trac(a)macosforge.org> Reply-To: noreply(a)macosforge.org To: ebgssth(a)gmail.com, macports-tickets(a)lists.macosforge.org Cc: mww(a)macports.org Date: Sat, Feb 16, 2008 at 12:18 PM #14342: python25 drops modules by default, but python25 doesn't --------------------------------+------------------------------------------- Reporter: ebgssth(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Resolution: | Keywords: python --------------------------------+------------------------------------------- Comment (by ebgssth(a)gmail.com) I think that's OK, but the thing is python24 doesn't drop these modules. It's a weird... -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14342#comment:3> [Quoted text hidden] -------- From: MacPorts <trac(a)macosforge.org> Reply-To: noreply(a)macosforge.org To: ebgssth(a)gmail.com, macports-tickets(a)lists.macosforge.org Cc: mww(a)macports.org Date: Sat, Feb 16, 2008 at 12:44 PM #14342: python25 drops modules by default, but python25 doesn't --------------------------------+------------------------------------------- Reporter: ebgssth(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Resolution: | Keywords: python --------------------------------+------------------------------------------- Comment (by raimue(a)macports.org) If we were going to change this, it would require to change dependencies in nearly all py-* ports. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14342#comment:4> [Quoted text hidden] -------- From: MacPorts <trac(a)macosforge.org> Reply-To: noreply(a)macosforge.org To: ebgssth(a)gmail.com, macports-tickets(a)lists.macosforge.org Cc: mww(a)macports.org Date: Sat, Feb 16, 2008 at 1:59 PM #14342: python25 drops modules by default, but python25 doesn't --------------------------------+------------------------------------------- Reporter: ebgssth(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Resolution: | Keywords: python --------------------------------+------------------------------------------- Comment (by ebgssth(a)gmail.com) Replying to [comment:4 raimue(a)macports.org] > If we were going to change this, it would require to change dependencies in nearly all py-* ports. Yes, we probably have to check py-ports that was not in py25 ports {{{ $ port list |egrep -i '^py-' | cut -d" " -f1 | sort -u > py24 $ port list |egrep -i '^py25-' | cut -d" " -f1 | sed 's/^py25/py/' | sort -u > py25 $ wc -l py2[45] 338 py24 109 py25 447 total $ comm -2 -3 py24 py25 > py24-only $ wc -l py24-only 259 py24-only }}} How about create py25- ports of all 259 py24 only ports? To create py25-ports, we need to know the port need zlib or hashlib, which helps identify this py24 ports should be fixed. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14342#comment:5> [Quoted text hidden] -------- From: MacPorts <trac(a)macosforge.org> Reply-To: noreply(a)macosforge.org To: ebgssth(a)gmail.com, macports-tickets(a)lists.macosforge.org Cc: mww(a)macports.org Date: Sat, Feb 16, 2008 at 6:27 PM #14342: python25 drops modules by default, but python25 doesn't --------------------------------+------------------------------------------- Reporter: ebgssth(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Resolution: | Keywords: python --------------------------------+------------------------------------------- Comment (by ebgssth(a)gmail.com) From a different point of view, that MacPorts has lots more python2.4 ports than python2.5's seems weird to me. (Python 2.5 is the current stable, Python 2.4 series will be no longer released anymore) Should I open another ticket about this problem? -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14342#comment:6> [Quoted text hidden] -------- From: MacPorts <trac(a)macosforge.org> Reply-To: noreply(a)macosforge.org To: ebgssth(a)gmail.com, macports-tickets(a)lists.macosforge.org Cc: mww(a)macports.org Date: Sat, Feb 16, 2008 at 9:33 PM #14342: python25 drops modules by default, but python25 doesn't --------------------------------+------------------------------------------- Reporter: ebgssth(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Resolution: | Keywords: python --------------------------------+------------------------------------------- Comment (by raimue(a)macports.org) Replying to [comment:5 ebgssth(a)gmail.com] > Yes, we probably have to check py-ports that was not in py25 ports No, py25-foo can have different dependencies than py-foo. I don't know what you wanted to tell us with this. And there is no problem that we have more py-* ports than py25-* ports. We just add what people request. If nobody needs a port, but it is in the tree, it is just more work for maintainers. So if you need some port, ask for it. PS: This kind of discussion would have been better on the mailing list. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14342#comment:7> [Quoted text hidden] --------

4 9

Python framework transition
by Rainer Müller 06 Mar '08

06 Mar '08

Hi Thomas, Following the IRC discussion from today with afb and mdickens, I wrote together a wiki page which documents how we want to do the transition to build pythonXX as frameworks. http://trac.macosforge.org/projects/macports/wiki/PythonFrameworkTransition Any comments so far? Also see the new branch at branches/python-frameworks. I already committed the efforts from #11267 there. With the branch, we can easily test the transition code. Rainer

2 3

RFC: MacPorts Filesystem Hierarchy Standard
by js 06 Mar '08

06 Mar '08

Hi, I wrote the Filename hierarchy standard for MacPorts. I know there's already porthier(7), but I thought it would be nice to have more specific standard. As you can see, this standard is still incomplete intentionally, becauses this kind of task should be not done in solely and I'd like to check if there are demands for this. I am really like to hear from all of you. Any comments, suggestions and even critique would be appreciated. Thanks. -------------------------------------------------------------------------------- MacPorts Filesystem Hierarchy Standard Purpose This document defines the standard placement of file and directory installed by MacPorts. This document also intended to replace the existing porthier(7)[1]. Every ports in MacPorts project should follow this standard. Most of this based on hier(7)[2]. Naming Convension When two or more ports have files in common, e.g. apachectl in apache and apache2, each port must prepend the part of its major version number to the files as a suffix. (e.g. apachectl for apache, apachectl2 for apapche2) When a port need to install multiple files, it must create a directory named its port name and installs the files in it. (e.g. macports/macports.conf, macports/mp_version) The Filesystem Prefix Everything installed by MacPorts must be in /opt/local or /Applications/MacPorts. The former is used for non-aqua applications and may be changed by modifying macports.conf. The latter is for aqua applications and cannot be changed. Non Aqua Applications ${prefix} contains the following directories. - bin contains common utilities, programming tools, and applications. - etc contains system configuration files and scripts. - include Standard C include files. - lib System libraries. - libexec System daemons and utilities (executed by other programs). For example, mysqld(a system daemon), apache/modules(a utility) - sbin System daemons and utilities (executed by users). for example, httpd(a system daemon), ifstat(a utility) - share - info Texinfo source files. - man - cat[0-9ln] - man[0-9ln] Manual pages. - nls National Language Support (NLS) catalogs. - (LANGS) - skel Example `.' (dot) files for new accounts. (FIXME: wonder we really need this) - src Doesn't exist... - var Multi-purpose log, temporary, transient and spool files. - macports - distfiles - receipts - registry - distfiles - software - sources - db Miscellaneous, automatically generated system-specific database files. For example, ... what? (Note that currently mysql data directory is created here. This is not correct.) - run System information files describing various info about the system since it was booted. For example, pid files. - log Log files. Every program in MacPorts should write it logs to this place. For example, var/log/apache/access, var/log/mysql/mysqld.err - www ServerRoot point for httpd(8). [1] MacPorts File Hierarchy http://guide.macports.org/#internals.hierarchy [2] OpenBSD Reference Manual HIER(7) http://www.openbsd.org/cgi-bin/man.cgi?query=hier&sektion=7

3 5

universal broken in trunk
by Emil Lundberg 06 Mar '08

06 Mar '08

In wanting to play around some more with 64-bit macports, I've installed 1.7 trunk (rev. 34799) from SVN on my PPC G5, 10.5.1. Installation went well but when I try to use the "universal" variant (no 64-bit stuff yet!) it breaks, like so: # port -d install jpeg +universal DEBUG: Found port in file:///opt/local/var/macports/sources/ rsync.macports.org/release/ports/graphics/jpeg DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/graphics/jpeg DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: Requested variant powerpc is not provided by port jpeg. DEBUG: Requested variant darwin is not provided by port jpeg. DEBUG: Requested variant macosx is not provided by port jpeg. DEBUG: Executing variant universal provides universal DEBUG: can't read "configure.universal_cflags": can't read "configure.universal_target": no such variable while executing "eval configure.cflags-append ${configure.universal_cflags}" (procedure "variant-universal" line 13) invoked from within "variant-universal" invoked from within "catch "variant-${name}" result" Error: Error executing universal: can't read "configure.universal_cflags": can't read "configure.universal_target": no such variable DEBUG: Error evaluating variants while executing "error "Error evaluating variants"" (procedure "mportopen" line 51) invoked from within "mportopen $porturl [array get options] [array get variations]" Error: Unable to open port: Error evaluating variants Same thing happens with any port if I set "+universal" in variants.conf. This all works fine on a different machine (PPC, G5, 10.4.11, trunk rev. 34088). Does anyone have a clue? TIA, /Emil

1 0

New HOWTO section in the wiki
by Rainer Müller 06 Mar '08

06 Mar '08

Hi, I started a new HOWTO section in the wiki [1]. These HOWTOs should cover tutorials and tips how specific things can be done using MacPorts. This is meant to be an addition to the guide and should not contain topics already covered by the guide. It is a place editable by everyone to share tips and tricks. So far I just added two HOWTOs to demonstrate how they should look like. If you have a good idea what such a HOWTO could cover, feel free to add it to the list. And if you even want to help by writing a HOWTO/tutorial yourself in order to make using MacPorts easier, there is a template which you can use as a start. So far I added two HOWTOs, one explaining how to use ccache and another how parallel building can be enabled. Of course you are free to edit them e.g. to add further information. Also, there is a list what could also be written. Even if you don't have time to write a HOWTO yourself, please make your mind what else could be useful and add it to that list. Rainer [1] http://trac.macosforge.org/projects/macports/wiki/howto

2 2