> On 11/03/2021, at 01:10, Antonio Rojas <nqn7...@gmail.com> wrote:
>
> El miércoles, 10 de marzo de 2021 a las 10:21:07 UTC+1, François Bissey
> escribió:
> Instead of trying to fix the problem that you should be building the
> documentation
> before installing, the push to modularisation is currently used to enshrine
> the
> current situation. #30010 actually separate the bits needed to build the sage
> documentation in a completely separate package.
> So the situation is now:
> * install package A
> * install package B
> * make a package C that takes B and applies it to the install of A and
> install
> the documentation of A (not C).
>
>
> Hi,
> As long as everything is still shipped in the Sage source tarball, isn't it
> just a matter of changing a path in the build script? I've always run the doc
> build directly from the Sage source, without installing anything, and I hope
> to be able to keep doing it that way (after a quick test, it still seems to
> be possible after #30010). Of course, if the long term plan is to split this
> to a separate git repo, then I completely share your concerns.
>
I’d like to talk to you on another channel, I have to do a small
patch currently. It may reflect different packaging strategy or
something I could improve.
François
--
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/C2A6536C-BCA9-4B7E-82C8-0D427886BF19%40gmail.com.
