Re: Splitting the guide

2008-03-06 Thread Rainer Müller
[EMAIL PROTECTED] wrote: >> I just tried this using DocBook but it didn't work for me. So I used a >> simple >> sed replacement to get this working. I created two examples: >> http://ruderich.com/macports/guide-link.html I like this one with the links. It makes it easy to get the URL which links

Re: RFC: MacPorts Filesystem Hierarchy Standard

2008-03-06 Thread js
> > 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

universal broken in trunk

2008-03-06 Thread Emil Lundberg
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 i

Re: RFC: MacPorts Filesystem Hierarchy Standard

2008-03-06 Thread Rainer Müller
js wrote: >>> - db >> > Miscellaneous, automatically generated system-specific database >> > files. For example, ... what? >> > (Note that currently mysql data directory is created here. This is >> > not correct.) >> >> No idea what is meant to reside here. Sure, mysqlX could also go

Re: RFC: MacPorts Filesystem Hierarchy Standard

2008-03-06 Thread js
> > BSDs save system-specific data like locate.database here. > > might be good place to put macports dir. > > var/macports moved from var/db/dports in the DarwinPorts -> MacPorts > rename effort. Any reason? ___ macports-dev mailing list macports-de

Re: RFC: MacPorts Filesystem Hierarchy Standard

2008-03-06 Thread markd
>> > 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

Python framework transition

2008-03-06 Thread Rainer Müller
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 th

Re: Python framework transition

2008-03-06 Thread Boyd Waters
> • because we change lib/python2.5 from a directory into a symlink. > Otherwise you will see errors with file_map.db. > • Because of the directory-to-symlink change, deactivate/activate > does not work. This will be the main challenge. > I think that this is why I haven't committ

Re: Python framework transition

2008-03-06 Thread Rainer Müller
Boyd Waters wrote: > I think that this is why I haven't committed anything; I've been > building all Python 2.5 stuff via MacPorts as a framework build for > about a year now. > > I had to modify all of my Python ports that I use so that they > understand the symlink. Should be working out-

Versioned ports (again)

2008-03-06 Thread Boyd Waters
Rainer: Thanks for the clarification! Ah, I see... put things in the portgroup. Of course... On Mar 6, 2008, at 11:48 AM, Rainer Müller wrote: >> I am pretty sure I don't understand all the issues, I still think >> that MacPorts versioning (-24, -25, -30) is profoundly flawed, >> aside fr