jmr at macports.org
Wed Feb 25 17:15:52 PST 2009
Bradley Giesbrecht wrote:
> On Feb 24, 2009, at 7:45 PM, Bill Hernandez wrote:
>> On Feb 24, 2009, at 7:03 PM, Scott Haneda wrote:
>>> On Feb 24, 2009, at 3:31 PM, Chris Janton wrote:
>>>> On 2009-02-24 , at 15:35 , Scott Haneda wrote:
>>>>> My feeling is, the sooner the better, there are already a handful
>>>>> of blogs out there, which instructions and hard paths in their
>>>>> instructions pointing to the current location. The sooner we put
>>>>> it where MacPorts recommends, the better the long term usability is
>>>>> going to be.
>>>> how about leaving it where it has been for years? I suspect many
>>>> people who use the port have become "attached" to the current
>>>> location, including me.
>> Please don't change it.
>> I wish mysql, pgsql, php were setup in individual directories like
>> That was one of the niceties of installing them individually in
> So we would add
> to our environment path?
> And when apache, mysql or pgsql data out grow your disks you would move
> all your bin, data and etc to another volume and change your paths and
> startup parameters so they could find the new location for configs?
> Data often needs to move. Binaries and configs hardly ever.
> I think Scott sees an inconsistency and an error with the macports
> apache2 install. That's hard to deny.
> Why not just park everything at /. No distribution I know of including
> apple will over write /apache2 and /mysql. Ok, now I'm kidding. Oh,
> maybe not.
This is starting to sound like GoboLinux. ;-)
More information about the macports-users