Re: [Pharo-users] Versionner: Specifying un-configured packages as dependencies

2014-05-24 Thread Arturo Zambrano
I think I'm now at the same point... I need to add Zinc-SSO as a dependency. Should I create a configuration for it? Where should it be stored? thanks On Thu, May 22, 2014 at 1:55 PM, stepharo steph...@free.fr wrote: + 100 The reason is that any package* should be self described. Your

Re: [Pharo-users] Versionner: Specifying un-configured packages as dependencies

2014-05-24 Thread Arturo Zambrano
Sorry, SSO is a Group in ConfigurationOfZincHTTPComponent. I got confused as I didn't know about groups. Please ignore my previous email, I just need to make my project depend on Zinc SSO group On Sat, May 24, 2014 at 10:58 PM, Arturo Zambrano arturo.zambr...@gmail.com wrote: I think

Re: [Pharo-users] Versionner: Specifying un-configured packages as dependencies

2014-05-23 Thread stepharo
+ 100 The reason is that any package* should be self described. Your configuration describes your project. If you use another piece of software, it should also be self-described. Let's take the following example: * for now, it's easy for you to add a direct dependency to Roassal2Spec,

Re: [Pharo-users] Versionner: Specifying un-configured packages as dependencies

2014-05-22 Thread Christophe Demarey
Le 22 mai 2014 à 01:02, Johan Fabry a écrit : On May 21, 2014, at 5:07 AM, Christophe Demarey christophe.dema...@inria.fr wrote: To me, it is preferable to add a configuration (even if very small) for each dependency outside your project. It is the way it should be done (that's why

Re: [Pharo-users] Versionner: Specifying un-configured packages as dependencies

2014-05-22 Thread Johan Fabry
On May 22, 2014, at 5:00 AM, Christophe Demarey christophe.dema...@inria.fr wrote: In general I am not so sure that adding configurations for one simple package are the way to go though. It seems like adding extra layers of indirection for reasons that are unclear to me. The reason is

Re: [Pharo-users] Versionner: Specifying un-configured packages as dependencies

2014-05-22 Thread Sean P. DeNigris
jfabry wrote I put a high priority on the simplicity rule It's good to know the dangers, but for single packages with no dependencies, I often just add it to my project. - Cheers, Sean -- View this message in context:

Re: [Pharo-users] Versionner: Specifying un-configured packages as dependencies

2014-05-21 Thread Christophe Demarey
Le 20 mai 2014 à 22:53, Sean P. DeNigris a écrit : Christophe Demarey wrote but it will not work as it is hosted on another repository Not that I'm recommending it, but if necessary, you could always copy it into your project's repo to get around that (or I think you can specify a

[Pharo-users] Versionner: Specifying un-configured packages as dependencies

2014-05-20 Thread Johan Fabry
Hi all, I’m using Versionner to make a ConfigurationOf and things are working quite well (thanks for that!) until I want to add the Roassal2Spec package as a dependency. The dialog box only shows packages with a configuration, and Roassal2Spec does not have one. It’s just one package. How can

Re: [Pharo-users] Versionner: Specifying un-configured packages as dependencies

2014-05-20 Thread Christophe Demarey
Hi, Le 20 mai 2014 à 15:01, Johan Fabry a écrit : Hi all, I’m using Versionner to make a ConfigurationOf and things are working quite well (thanks for that!) until I want to add the Roassal2Spec package as a dependency. The dialog box only shows packages with a configuration, and

Re: [Pharo-users] Versionner: Specifying un-configured packages as dependencies

2014-05-20 Thread Sean P. DeNigris
Christophe Demarey wrote but it will not work as it is hosted on another repository Not that I'm recommending it, but if necessary, you could always copy it into your project's repo to get around that (or I think you can specify a repository in the #with: block of the package spec. -