Bug 259963

Summary: ports-mgmt/octopkg consider not using -f -y (force) by default
Product: Ports & Packages Reporter: Graham Perrin <grahamperrin>
Component: Individual Port(s)Assignee: freebsd-ports-bugs (Nobody) <ports-bugs>
Status: Closed Works As Intended    
Severity: Affects Some People CC: fernape
Priority: ---    
Version: Latest   
Hardware: Any   
OS: Any   
URL: https://github.com/aarnt/octopkg/issues/14
Attachments:
Description Flags
Screenshot: -f -y none

Description Graham Perrin freebsd_committer freebsd_triage 2021-11-21 14:10:50 UTC 
Created attachment 229634 [details]
Screenshot: -f -y

Can there be a preference to not force things by default? 

In some cases, removals – for which there's no forewarning – might be troublesome. 

<https://github.com/aarnt/octopkg/issues/3#issuecomment-183935274> it's possible to cancel an in-progress transaction, but avoidance will be preferable. 

Thanks
Comment 1 Fernando Apesteguía freebsd_committer freebsd_triage 2021-11-24 07:49:19 UTC 
(In reply to Graham Perrin from comment #0)
Hi Graham,

Thanks for the PR. Wouldn't this be something to be reported upstream instead?
Comment 2 Graham Perrin freebsd_committer freebsd_triage 2021-11-24 21:37:58 UTC 
(In reply to Fernando Apesteguía from comment #1)

Ah, I assumed that use of -f was specific to pkg i.e. FreeBSD.
Comment 3 Graham Perrin freebsd_committer freebsd_triage 2021-11-24 21:54:28 UTC 
(I thought that my first encounter of OctoPkg was on a Linux-based system, and that this behaviour was specific to a port from Linux to FreeBSD. In retrospect, the first encounter was probably _Octopi_, hence my confusion. Sorry.)

Works as intended by upstream. 

Await the outcome of <https://github.com/aarnt/octopkg/issues/14>.