MacPorts 1.6 still supports OS X 10.3 Panther?

[Kevin Ballard]

Once you have svn installed, simply navigate to the directory you want  
to check out the source into (into a subfolder, that is) and run the  
following command:

svn checkout http://svn.macports.org/repository/macports/trunk/base  
macports

This will check out the macports source into a folder called macports.  
You can then execute the following:

cd macports
./configure
make
sudo make install

This will overwrite your previous macports installation (but leave  
your installed ports untouched). If you do this, you should continue  
to update your ports tree with `sudo port sync` but never run `sudo  
port selfupdate` or you risk overwriting your macports installation  
with a released version instead of one from source. To update to the  
latest in the future, simply run:

cd path/to/macports
svn update
make
sudo make install

Please note that this is deliberately not giving you an svn checkout  
of the dports tree, in the interests of saving time. If you want a  
checkout of the dports tree itself, remove the trailing /base from the  
URL above, and instead navigate to macports/base before building. Of  
course, if you do this you also have to edit your /opt/local/etc/ 
macports/source.conf file to point to your dports checkout instead of  
the rsync server.

-Kevin Ballard

On Jan 6, 2008, at 7:08 PM, Chris Janton wrote:

> On 2008-01-06 , at 14:44 , Ryan Schmidt wrote:
>
>> Ok, so you've discovered that Kevin's latest attempt did not fix  
>> the issue.
>>
>> Perhaps you could try what I suggested to discover which change  
>> caused the issue in the first place?
>>
>> http://lists.macosforge.org/pipermail/macports-users/2008-January/008061.html
>
>
>> Probably what we should do first is determine the specific commit /
>> revision / changeset that broke the build on Panther. I don't think
>> we've established that yet. My wild guess was revision 29498. To test
>> whether that's the culprit, check out trunk at r29497 and build it on
>> Panther. If it builds, then check out trunk at r29498 and build it.
>> If it fails, then r29498 broke the build, and we can further analyze
>> the changes made in that revision.
>>
>
> OK. I can do that. Just a tiny bit more help (I'm good at following  
> directions, but not so good at understanding the ins and outs of svn)
>
> How do I
>
> 	"check out trunk at r29497"
>
> I assume that the configure, make, sudo make install apply for all  
> of the tests.
> Once I figure out how to check out the right copy of the source I  
> can apply the same method again (and again, and again...)
>
> Thanks.
>
> 8)
> ----------------------------------
> Chris Janton  - face at CentosPrime dot COM
> Netminder for Opus1.COM
>
>

-- 
Kevin Ballard
http://kevin.sb.org
eridius at macports.org
http://www.tildesoft.com