Thanks for the example use-case.
My personal favorite for the name so far is "noupdate", and quite clearly it
should not be tied to %config because the use-cases for this thing are actually
something quite different. It probably should behave differently when applied
to %config though - it could contain precious user data that you'd want to
backup in some cases, but eg the vagrant plugin case clearly is not such.
Other musings on the name subject: the content in this case acts as a seed
only, but maybe %seed is too far fetched. Another related point is that these
files are managed by something else than rpm, so %managed comes to mind, but
then that sounds like something where the content would come entirely outside
rpm, and that's not a packaging-time decision (or when it is, it's satisfied
with %ghost)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/152#issuecomment-278892642
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
