I haven't been following the copy and paste thread, but I'm in favor of
keeping sage -i xyz functional, even at the cost of some hacks in our
codebase.  There are a lot of existing Sage users who are familiar with
that command as a mechanism to install optional packages, even if it's not
a priori discoverable for new users of Sage.
David

On Fri, Apr 22, 2022 at 2:02 PM Michael Orlitzky <mich...@orlitzky.com>
wrote:

> On Fri, 2022-04-22 at 08:16 -0700, seb....@gmail.com wrote:
> >
> > (./sage -i should be deprecated and removed…)
> >
> > — or just have ‘sage -i xyz’ do whatever ‘make xyz’ now does, perhaps.
> >
> > +1
> >
>
> This only works if you don't ever want to e.g. rename sage to sage.in
> to fix the copy & paste from the other thread.
>
>
> > Replacing sage -i xyz by make xyz sounds like assuming *all Sage users
> are
> > developers*.
>
> Neither approach assumes anything, but using "make" is at least
> familiar to anyone who has built any unix software in the past 30
> years. The ad-hoc "sage" stuff is a priori familiar to no one and
> prevents us from modernizing lots of old cruft.
>
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/71d0b974600eb89959f8ad309ba4bd7f3f31d777.camel%40orlitzky.com
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAChs6_ng6aW%2BTF9DRSxwks_5fTKaH7y6f7q8hLQhGnAmhuSNNA%40mail.gmail.com.

Reply via email to