Administrator
|
We (Cami, Ben, and I) added some command line options to control preference loading, which seem useful e.g. for integrators and in my original use case of running an image off a USB stick on a foreign computer and not wanting to pick up those preferences
There are two new flags: 1. --no-default-preferences = don't load from any of the default locations 2. --preference-file [/full/path/to/file.st] = load this one They are independent, so there are four options now: 1 | 2 | - current behavior x - don't load any preferences x - load the defaults and this additional x x - only load the specified file (not the defaults)
Cheers,
Sean |
Good news.
If by default on Windows, it would be another default than pharo\ it would be great as it would be nicer with zeroconf fetching pharo-ui and pharo (headless)
Are those changes going to find their way in Pharo 2.0? Phil On Thu, Oct 10, 2013 at 7:48 PM, Sean P. DeNigris <[hidden email]> wrote: We (Cami, Ben, and I) added some command line options to control preference |
In reply to this post by Sean P. DeNigris
excellent I will update the StartUp script chapter (except if somebody wants to do it).
On Oct 10, 2013, at 7:48 PM, "Sean P. DeNigris" <[hidden email]> wrote: > We (Cami, Ben, and I) added some command line options to control preference > loading, which seem useful e.g. for integrators and in my original use case > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/New-Image-Command-Line-Handlers-tp4713693.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > |
Administrator
|
In reply to this post by philippeback
It doesn't really fit our "backport bug fixes only" policy. When I backported the completion stuff because it was too cool not to, it was a week-long hassle chasing collateral bugs. But what I've been doing for these types of things is merging into the released version, saving the packages online, and customizing my own images with them. It's been working pretty well since the released versions don't change very much.
HTH -------- Original message -------- From: "philippeback [via Smalltalk]" <[hidden email]> Date: 10/10/2013 2:10 PM (GMT-05:00) To: "Sean P. DeNigris" <[hidden email]> Subject: Re: New Image Command Line Handlers Good news.
If by default on Windows, it would be another default than pharo\ it would be great as it would be nicer with zeroconf fetching pharo-ui and pharo (headless)
Are those changes going to find their way in Pharo 2.0? Phil On Thu, Oct 10, 2013 at 7:48 PM, Sean P. DeNigris <[hidden email]> wrote: We (Cami, Ben, and I) added some command line options to control preference If you reply to this email, your message will be added to the discussion below:
http://forum.world.st/New-Image-Command-Line-Handlers-tp4713693p4713697.html
Cheers,
Sean |
This is great. However, I vote against backporting to Pharo 2.0. Pharo 3.0 is close to be frozen and I think the efforts should be focused on that right now. Doru On Fri, Oct 11, 2013 at 2:09 AM, Sean P. DeNigris <[hidden email]> wrote: It doesn't really fit our "backport bug fixes only" policy. When I backported the completion stuff because it was too cool not to, it was a week-long hassle chasing collateral bugs. But what I've been doing for these types of things is merging into the released version, saving the packages online, and customizing my own images with them. It's been working pretty well since the released versions don't change very much. "Every thing has its own flow"
|
Administrator
|
In reply to this post by philippeback
If you need them, you can try to load the Backport-Pharo-Issue-11571-to-20 package from http://ss3.gemstone.com/ss/PharoSpd. Two caveats: 1. there is a post-load doit 2. I haven't tested the changes in 2.0 HTH
Cheers,
Sean |
Free forum by Nabble | Edit this page |