-
Notifications
You must be signed in to change notification settings - Fork 461
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
apt: Add apt::setting defined type. #428
Conversation
581e283
to
21ff418
Compare
} | ||
|
||
if $type == 'list' { | ||
$_priority = '' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we have a warning if $type == 'list' and $priority
, or is this obvious to apt users?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Priority doesn't make sense for list, it's not a concept that sources recognise so there's no real use or need for it. We should document that we ignore priority in that case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, cool. At some point there will be massive doc updates, I ... haven't been keeping up with that.
@daenney commented, assigned back to you for response. |
This is a 'base' type. It's a simple wrapper around a file which takes `type`, `ensure`, `content`, `source` and `file_perms`. It is intended for usage by `apt::conf`, `apt::source` and an upcoming `apt::pref`.
21ff418
to
76c88af
Compare
apt: Add apt::setting defined type.
Thanks @daenney ! |
This is a 'base' type. It's a simple wrapper around a file which takes
type
,ensure
,content
,source
andfile_perms
. It is intended for usage byapt::conf
,apt::source
and an upcomingapt::pref
.