[38028] trunk/dports/PortIndex

Daniel J. Luke dluke at geeklair.net
Mon Jul 7 13:20:04 PDT 2008

On Jul 7, 2008, at 4:15 PM, William Siegrist wrote:
> From reading the script, it makes yet-another-checkout/update of the  
> source instead of coexisting with PortIndex2MySQL and mprsyncup?


> It also reinstalls MP v1.6 every time?

Well, it reinstalls the current release every time (I never bothered  
to make the script smarter to only install if the release changed).

> I run MP from trunk on the servers, and carefully jump to new  
> versions, so I'd like to avoid reverting to 1.6 and/or getting a new  
> MP install every day automatically.

Its install is not system-wide, if that helps any. On my box, it all  
lives in its own user's $HOME

> I can probably unify the various scripts to all update to the same  
> place so I dont have so many copies of MP source  laying around, but  
> I was curious if the index *must* be done from a machine running the  
> latest release instead of a reasonably-up-to-date trunk install?

Yes. The PortIndex should only contain ports which can be parsed by  
the current MacPorts release, so the portindex that generates it needs  
to be from the current release. A newer version, which supports newer  
keywords would add ports to the index that users running the latest  
release version wouldn't be able to install.

Daniel J. Luke
| *---------------- dluke at geeklair.net ----------------* |
| *-------------- http://www.geeklair.net -------------* |
|   Opinions expressed are mine and do not necessarily   |
|          reflect the opinions of my employer.          |

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part
Url : http://lists.macosforge.org/pipermail/macports-dev/attachments/20080707/33962803/attachment.bin 

More information about the macports-dev mailing list