[General] New URL needed...

[Ted Leung]

I looked in the files tonight, when I was trying to figure out how to  
launch Chandler in a source build now that the RunChandler scripts  
are nuked.

Ted

On Jul 13, 2007, at 4:30 PM, Sheila Mooney wrote:

> Bear had sent me an email with all the current files we use today.  
> Yes, the linux one got changed. Sorry, I meant to forward to the  
> list. I will be working from these.
>
> <README.linux.txt><README.osx.txt><README.win.txt>
> I don't have any strong opinion about the URLs. I don't know that  
> anybody ever looks at these files anyway. I believe we missed  
> updating one last time and nobody reported it.
>
>
> On Jul 13, 2007, at 4:22 PM, Philippe Bossut wrote:
>
>> Hi,
>>
>> Some of the technical aspects of this ReadMe go beyond URLs so I'm  
>> cc-ing bear so that it gets his attention. My comments in-line:
>>
>> Sheila Mooney wrote:
>>> Chandler README.linux
>>> ---------------------
>>>
>>> * Compatibility *
>>>
>>> Our Linux binaries are built on a computer running Fedora Core 2.
>> It's Ubuntu (Dapper) last time I checked (Bear? Confirm?). Our  
>> build actually does not run on FC 2 (though you can build on it  
>> and it should work...).
>>>
>>> For details on the various platforms that Chandler has been built
>>> for, and also those that can run the binaries, please see:
>>>
>>>   http://wiki.osafoundation.org/bin/view/Projects/ChandlerPlatforms
>>
>> We do have such a list at http://chandlerproject.org/Developers/ 
>> ChandlerDesktopSource#Detailed%20Platform%20Reports but having a  
>> nicer URL will help.
>>>
>>> If you are building Chandler yourself you will need a few extra
>>> things.  For details on how to build, please see:
>>>
>>>   http://wiki.osafoundation.org/twiki/bin/view/Projects/ 
>>> BuildingChandler
>> http://chandlerproject.org/Developers/BuildingChandlerDesktop.  
>> This one URL seems good enough for a ReadMe.
>>>
>>> * Running Chandler *
>>>
>>> To run chandler, use the executable "RunChandler" in the release  
>>> or debug
>>> directory, like so:
>>>
>>>   % ./release/RunChandler
>>>
>>> or, if you have a "debug" version:
>>>
>>>   % ./debug/RunChandler
>>>
>>> If you aren't sure which you have, you can run:
>>>
>>>   % ./*/RunChandler
>>
>> Ooops... Following up on Bear's taking RunChandler out (http:// 
>> lists.osafoundation.org/pipermail/chandler-dev/2007-July/ 
>> 008531.html), this needs to be updated. I'm not the Linux guru/ 
>> expert here so I'll let Bear or Heikki speak. Apparently though,  
>> the right method is to do:
>>
>> ./release/RunPython -O Chandler.py
>>
>> or
>>
>> ./debug/RunPython -O Chandler.py
>>>
>>> * Latest Release *
>>>
>>> Download the new Chandler 0.7Alpha4 milestone for a sneak peak at  
>>> features we are implementing for the 0.7 release. For more  
>>> details go to...
>>>
>>> http://chandler-dev.osafoundation.org/newinalpha4.php
>>>
>> Needs to be update of course but I guess you have a handle on that  
>> one.
>>
>> Cheers,
>> - Philippe
>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>>
>> Open Source Applications Foundation "General" mailing list
>> http://lists.osafoundation.org/mailman/listinfo/general
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "General" mailing list
> http://lists.osafoundation.org/mailman/listinfo/general