Opened 5 years ago

Closed 4 years ago

Last modified 4 years ago

#20937 closed defect (duplicate)

Document new -y switch of "sage -i"

Reported by: mkoeppe Owned by: embray
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: build Keywords:
Cc: embray, dimpase, novoselt, vbraun Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: #20884 Stopgaps:

Status badges

Description

Follow up on #20884:

The newly added -y switch should be added to the help screen obtained by sage -advanced.

And perhaps also in the manual (didn't look).

Change History (12)

comment:1 follow-up: Changed 5 years ago by embray

#20884 isn't merged yet so did this really need an additional ticket?

I didn't add the -y switch to sage though, but just just sage-spkg. I guess sage -i can pass arguments through to it though?

comment:2 in reply to: ↑ 1 Changed 5 years ago by mkoeppe

Replying to embray:

#20884 isn't merged yet so did this really need an additional ticket?

I opened a new ticket to avoid another race with the release manager.

I didn't add the -y switch to sage though, but just just sage-spkg. I guess sage -i can pass arguments through to it though?

I think it does.

comment:3 Changed 5 years ago by embray

I mostly added it as an internal interface between the two. But I guess I can see how it might be useful, especially for someone developing an experimental package.

comment:4 Changed 5 years ago by embray

  • Dependencies set to #20884

comment:5 Changed 5 years ago by mkoeppe

What I meant to say is, there needs to be a documented switch for "sage -i" and "sage -f" that enables installing experimental packages without asking questions. Right now -y seems to work; so that could be documented; however, if there is a different switch, that's also fine if that is documented.

comment:6 Changed 5 years ago by embray

No, -y would be it. I just didn't realize before you posted this ticket that there was a need for that at all (I only added it specifically for the sake of running make directly). But like I said, now that you bring it up, I can see the potential use.

I'm happy to add docs for it in the help once #20884 is done.

comment:7 Changed 5 years ago by embray

  • Owner changed from (none) to embray

comment:8 Changed 4 years ago by mkoeppe

  • Milestone changed from sage-7.3 to sage-duplicate/invalid/wontfix
  • Status changed from new to needs_review

This is now done as part of #21082, so it can be closed.

comment:9 Changed 4 years ago by novoselt

  • Status changed from needs_review to positive_review

comment:10 Changed 4 years ago by mkoeppe

Thanks!

comment:11 Changed 4 years ago by mkoeppe

  • Resolution set to duplicate
  • Status changed from positive_review to closed

comment:12 Changed 4 years ago by novoselt

Um, I thought that only release manager is allowed to close tickets - have I missed something?

Note: See TracTickets for help on using tickets.