Re: New virtual packages: lv2-plugin and lv2-host
Jonas Smedegaard writes ("Re: New virtual packages: lv2-plugin and lv2-host"):
> It seems to me that you are applying more strict rules now than has been
> applied to other names on the list in the past.
This is not some kind of hazing ritual where people have to persuade a
reluctant audience. I'm just trying to make sure that we understand
what these virtual package names are for. And past decisions are not
necessarily a good guide in a relatively lightweight process like this
Do users specifically find LV2 plugin packages by name and install
them ? How does it help the user to have an arbitrary "lv2-host"
installed too ?