non-specific dependencies

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

non-specific dependencies

Julian Fitzell-2
On Sun, Jun 27, 2010 at 6:54 PM, Dale Henrichs <[hidden email]> wrote:

> Once you've loaded one of these configs, there will be no development tools
> nor any adaptors so at a minimum you'll need to load one of the following
> depending upon which adaptor you want to use:
>
>  "All platforms"
>  (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15')
>    load: #('Seaside-Adaptors-Swazoo').
>  "Squeak and Pharo"
>  (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15')
>    load: #('Seaside-Adaptors-Comanche').
>  "GemStone"
>  (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15')
>    load: #('Seaside-Adaptors-FastCGI').

This, of course, is why package management systems like RPM and Deb
end up having "provides". This would allow Seaside-Base to require
"http-adaptor" or something and each of those packages to provide
"http-adaptor". The package manager can then look for possibilities
and prompt if it finds more than one.

Not saying you need to go that route, but it's probably the
"traditional" solution.

Julian

_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
Reply | Threaded
Open this post in threaded view
|

Re: [Seaside] non-specific dependencies

Dale Henrichs
Thanks Julian ... I wasn't fishing for Metacello features, but this
sounds like something I will certainly look into adding to Metacello in
the future.

Dale

Julian Fitzell wrote:

> On Sun, Jun 27, 2010 at 6:54 PM, Dale Henrichs <[hidden email]> wrote:
>> Once you've loaded one of these configs, there will be no development tools
>> nor any adaptors so at a minimum you'll need to load one of the following
>> depending upon which adaptor you want to use:
>>
>>  "All platforms"
>>  (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15')
>>    load: #('Seaside-Adaptors-Swazoo').
>>  "Squeak and Pharo"
>>  (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15')
>>    load: #('Seaside-Adaptors-Comanche').
>>  "GemStone"
>>  (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15')
>>    load: #('Seaside-Adaptors-FastCGI').
>
> This, of course, is why package management systems like RPM and Deb
> end up having "provides". This would allow Seaside-Base to require
> "http-adaptor" or something and each of those packages to provide
> "http-adaptor". The package manager can then look for possibilities
> and prompt if it finds more than one.
>
> Not saying you need to go that route, but it's probably the
> "traditional" solution.
>
> Julian
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki