Issue 5796 in pharo: Integrate OSProcess

Status: Accepted
Owner: [hidden email]
Labels: Type-Bug Milestone-2.0

New issue 5796 by [hidden email]: Integrate OSProcess
http://code.google.com/p/pharo/issues/detail?id=5796

I heard OSProcess is going to be integrated within Pharo. Please close this  
report as soon as it is done as other issues depend on it.l


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Issue 5796: Integrate OSProcess
http://code.google.com/p/pharo/issues/detail?id=5796

This issue is now blocking issue 5780.
See http://code.google.com/p/pharo/issues/detail?id=5780

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #2 on issue 5796 by [hidden email]: Integrate OSProcess
http://code.google.com/p/pharo/issues/detail?id=5796

Parts/all of CommandShell-Piping should be included. At minimum,  
PipeableOSProcess is the only way to get input and output from OSProcesses.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #4 on issue 5796 by [hidden email]: Integrate OSProcess
http://code.google.com/p/pharo/issues/detail?id=5796

yes we should integrate this!!

but we will have to fork / modify / adapt a bit.
The current implementation lacks of simple interface methods like:

'ls -algh' command
'ls -algh' execute

And in most cases we care about the returned strings not the return status!


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: FixToInclude

Comment #5 on issue 5796 by [hidden email]: Integrate OSProcess
http://code.google.com/p/pharo/issues/detail?id=5796

So we should integrate OSProcess and PipepableProcess!

see http://book.pharo-project.org/book/PharoTools/OSProcess/

  Gofer new
        squeaksource: 'MetacelloRepository';
        package: 'ConfigurationOfOSProcess';
        load.
   (Smalltalk at: #ConfigurationOfOSProcess) project bleedingEdge load.

   Gofer new
        squeaksource: 'CommandShell';
        package: 'CommandShell-Piping';
        load.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: OnHold

Comment #6 on issue 5796 by [hidden email]: Integrate OSProcess
http://code.google.com/p/pharo/issues/detail?id=5796

We should first finish integrating SSL: lots of tests failing there. There  
are *lots* failing tests related to FS, too.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Cc: [hidden email] [hidden email]
        Labels: -Type-Bug Type-Feature

Comment #7 on issue 5796 by [hidden email]: Integrate OSProcess
http://code.google.com/p/pharo/issues/detail?id=5796

When we revisit this, are are some ideas from  
http://forum.world.st/pharo-monkey-issue-updater-tp4637322p4637376.html :

Esteban suggested:
'ls -la' systemTo: [ :stream | ]. "piped"
'ls -la>z' system. "non piped"

To which I replied:
That's clean enough, and very easy to implement...
ByteString>>system

         | process |
         process := PipeableOSProcess waitForCommand: self.
         ^ process output.

Of course, with the current implementation of OSProcess, it's very easy to  
hang the image that way, so we might want to #setNonBlockingOutput, or do  
our own polling...


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #8 on issue 5796 by [hidden email]: Integrate OSProcess
http://code.google.com/p/pharo/issues/detail?id=5796

sounds fine! Is #systemStreamTo: too long? might make the streaming point a  
bit clearer..

Though technically speaking OSProcess doesn't do a system call :P (but we  
will change that at some point I think)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: FixToInclude

Comment #9 on issue 5796 by [hidden email]: Integrate OSProcess
http://code.google.com/p/pharo/issues/detail?id=5796

(No comment was entered for this change.)

Attachments:
        LoadOSProcess.st  245 bytes


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: HumanReviewNeeded

Comment #10 on issue 5796 by [hidden email]: Integrate OSProcess
http://code.google.com/p/pharo/issues/detail?id=5796

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: OnHold

Comment #11 on issue 5796 by [hidden email]: Integrate OSProcess
http://code.google.com/p/pharo/issues/detail?id=5796

sorry, this is too much for now (we are trying to stabilize things)
(also OSProcess needs a clean up)
It would probably be better to defer this to 3.0 (next year)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Labels: -Milestone-2.0

Comment #12 on issue 5796 by [hidden email]: Integrate OSProcess
http://code.google.com/p/pharo/issues/detail?id=5796

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker