ports/101310: proposal: OPTION_VERSION in port system

Heiner Eichmann h.eichmann at gmx.de
Thu Aug 3 09:50:28 UTC 2006


>Number:         101310
>Category:       ports
>Synopsis:       proposal: OPTION_VERSION in port system
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Thu Aug 03 09:50:21 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Heiner Eichmann
>Release:        5.3
>Organization:
Sirius Cybernetics Corp.
>Environment:
>Description:
In order to configure a port, it is recommended, that the porter uses the OPTIONS variable in the port. If the user
installs the port, the options are shown and the choices are used to build the port. Furthermore these choices are strored.
If the port is upgrade or reinstalled, the stored choices are used. The only problem is: if the porter changes the options
(e.g. adding new options or changing the meaning of existing ones), the port user will not notice it.

A solution could be an additional variable: OPTION_VERSION. The porter should set it to a number. This number is stored 
together with the users choices. Just two rules are necessary:

- if the porter chnages the options, increment the OPTION_VERSION number in the ports Makefile
- if a port is built and the Makefiles OPTION_VERSION if higher than the OPTION_VERSION of the stored choices, show the
option dialog again, using the proviously stored choices, if possible.

With this two rules the user will always be aware of an options change of a port.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list