If there's a growing list of boolean control fields, isn't it the
indication that some sort of tagging system might make more sense?
Instead of three lines:
XB-Popcon-Reports: no
Rules-Requires-Root: yes
Pants-Need-Washing: yes
The same package could use a single line:
Tags: no-popcon-reports, rules-needs-root, pants-need-washing
(aside: by default rules doesn't need root... that would make one not- very-useful line less in so many packages!)
Some of our tools might provide easy queries to the feature:
$ apt-cache has-tag rules-needs-root my-beautiful-package
$ apt-cache list-tags my-beautiful-package
First, strictly speaking it's not boolean, at least until #975637 is implemented.If there's a growing list of boolean control fields, isn't it the indication that some sort of tagging system might make more sense?
Instead of three lines:
XB-Popcon-Reports: no
Rules-Requires-Root: yes
Pants-Need-Washing: yes
The same package could use a single line:
Tags: no-popcon-reports, rules-needs-root, pants-need-washing
ACK.
(aside: by default rules doesn't need root... that would make one not- very-useful line less in so many packages!)
I'd like to stress this! If "rules-needs-root: no" would be default
the majority of packages could be build. So why not making this the
default and just specify
rules-needs-root: yes
if needed?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (2 / 14) |
Uptime: | 146:10:20 |
Calls: | 10,383 |
Calls today: | 8 |
Files: | 14,054 |
D/L today: |
2 files (1,861K bytes) |
Messages: | 6,417,699 |