+1 to having another marker for those alternative-to-standard packages, but 
I think this is a bit of a problem to do in some general framework. These 
packages are suppose to come in sets and one of them will have to be 
installed. So it might be better to think of ways to combine these packages 
under common descriptions that the user could swap out by rebuilding.

Best,
Travis


On Tuesday, February 28, 2017 at 11:20:23 AM UTC-6, Thierry 
(sage-googlesucks@xxx) wrote:
>
> Hi, 
>
> having the possibility to install all optional packages is interesting for 
> easy deployment as well as for testing (we need more automated tests of 
> all optional packages, in particular more patchbots with optional packages 
> installed). Currently, some optional packages, like gmp/mpir, 
> atlas/openblas, boost/boost_cropped (what else ?) are alternatives to some 
> existing standard packages. Hence, those should not be installed when we 
> want to set up a patchbot to test optional packages (unless we want to 
> specifically test those). There is also the special case of openssl, which 
> should not be installed when openssl-dev is present on the system. 
>
> I would like to suggest to have such 
> replacement/duplicate/redundent/alternative/...  packages be tagged not as 
> 'optional' but with another word, so as to ease the selection and 
> installation of all optional packages, in order to easily provide some 
> kind of "sage-full" binaries and patchbots. I currently use a hand-made 
> list of optional packages for Sage Debian Live but it requires to be 
> updated at each release. 
>
> - What do you think about distinguish such packages to optional ones ? 
> - Which name should be given to such packages ? 
> - What are your current strategies to install all meaningful optional 
>   packages ? 
>
> Ciao, 
> Thierry 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to