On Wed, Nov 23, 2022 at 09:05:47PM -0500, Ionen Wolkens wrote: > On Thu, Nov 24, 2022 at 01:32:04AM +0000, Alexey Sokolov wrote: > > > However, I tend to agree that the category should be named app-meta > > > rather than sys-meta, because chances are that non-system packages will > > > also make use of it. > > > > > > Ulrich > > > > Since these packages manage symlinks, make it app-symlink? > > Mentioned this in another post, but this is limiting what would make > sense to be in there further. > > app -> what if it's library alternatives? > symlink -> what if we need to use wrappers or some other solution?
Then again, I guess installing a wrapper / config files, etc... won't fall under metapackage anymore, given installing code vs just making a symlink. > > Not that we ever really match categories perfectly either way, but > may as well stay generic rather than mismatch or create multiple > sub-types. > > Some random ideas I had were 'alternatives', 'meta', 'select' > 'select-meta', not that I thought much about it. > > 'meta' would essentially be like an entirely generic 'virtual' but > just without PMS restrictions. While the ones with alternatives or > select are more descriptive of what it's for without saying anything > about how we're doing it or for what type of package. > -- > ionen -- ionen
signature.asc
Description: PGP signature
