> Ok. Just to check. Are you advocating that leaving out cairo as a dependency of the main pharo app for new pharo users is a 'feature'?
Until Bloc it is a feature, but if it is installed via package manager then it should imho also install cairo because that's not that hard there. The problem is the VM downloaded via zeroconf. Sorry I don't explain myself properly. I was meaning a window with this > message instead of a error trace, which could be intimidating. Something > with the same message and buttons like "Ok", "Launch debugger". In the > workshops there are some Gnu/Linux newbies and the hidding the error trace > for a while seems to be helpful to them. This should be relatively simple to do: 1) create new "PreDebugger" that's user-friendly (currently we have (GT)SpecPreDebugWindow that is started from (GT)SpecDebugger>>openWithNotification:) 2) let Debuggers ask for PreDebugWindow class through Smalltalk tools 3) install your UserFirendlyPreDubugWindow to Smalltalk tools I think this would be a very useful addition for many people. (I wanted to make this some time ago but haven't got around to do it yet.) No, but because we could build a wrapper for particular packages that > installs Nix, and then others (32 bits variants of libcairo or sqlite, > pandoc, etc) without caring about a particular Unix variant (being them Mac > or hundreds Gnu/Linux distros based on dozen of "bases"), making the > experience smother for the newbie, providing he/she has root privileges. > People will not see nix anywhere, not even for installing Mac is self-contained, so the main issue is linux. If the user has a root privilege, then maybe we should push for pharo directly in the package manager repository? And sure, there are hundreds of distros, but you will cover majority of the market with… maybe 5 distros? People that can't handle obscure distros don't install them. But to get some motion: 1) let's compile a list of majority distros 2) let's see how hard it is to build packages for them (imho this could be automated via CI), and we already have ubuntu package (or maybe nix can be pushed to all distros?) 3) maybe consider all-in-one bundle for non-root targets (this would work for cairo, but not for 64b systems in general, because the dependency list there is monstrous) So no need to be sarcastic here Peter. Sorry, I got carried away. I've got my fair share of dependency hell and introducing another package manager always makes me shiver. On Thu, Mar 10, 2016 at 4:40 PM, Stephan Eggermont <step...@stack.nl> wrote: > On 10-03-16 15:28, Thierry Goubier wrote: > >> Recommande: pharo-vm-core:i386 >> >> pharo-vm-core suggest pharo-vm-desktop, and pharo-vm-desktop only >> recommand libcairo2 ? >> So, maybe we need to change the dependencies then ? >> > Yes, that sounds wrong. I would assume it to be: > Pharo launcher is a desktop application, > and the desktop needs Cairo. Core should be headless. > > Stephan > > >
