wsiegrist at apple.com
Mon Jul 7 17:01:36 PDT 2008
On Jul 7, 2008, at 1:20 PM, Daniel J. Luke wrote:
> 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
> 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.
Ok. I've setup a job to run at 00:45 and 12:45. You can disable it on
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 2421 bytes
Desc: not available
Url : http://lists.macosforge.org/pipermail/macports-dev/attachments/20080707/0e0b7118/attachment-0001.bin
More information about the macports-dev