gap is standard, gap_packages is optional $ cat build/pkgs/gap/type standard $ cat build/pkgs/gap_packages/type optional
On Tuesday, January 1, 2019 at 12:50:55 PM UTC+1, Simon King wrote: > > On 2019-01-01, Samuel Lelievre <samuel....@gmail.com <javascript:>> > wrote: > > Ticket 26856 should fix that. > > > > https://trac.sagemath.org/ticket/26856 > > Should fix *what* exactly? > > OK, I understood that database_gap got merged into gap_packages. But is > gap_packages now standard? In that case, one has to *remove* > "database_gap" from the list of dependencies. Or is gap_packages still > optional? In that case, one has to *replace* "database_gap" by > "gap_packages" in the list of dependencies. > > Looking at the diff on #26856, it seems that it is the former. But > please confirm, before I do something wrong when resolving the merge > conflict with #26001. > > Best regards, > Simon > > -- 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.
