New comment by lane-brain on void-packages repository

https://github.com/void-linux/void-packages/issues/26981#issuecomment-739566417

Comment:
It's a reality that proprietary software will tend to target Ubuntu, but I'm also aware that proprietary software isn't void's focus. I'm sympathetic for this use case however, there happens to be a template for bitwig studio that uses the `ar x` method @jrigg described. 

I think that xdeb did something useful, which was write the script that extracts the dependencies and converts them to their xbps equivalents. I'm looking over the script just to see exactly how xdeb constructs the package. It would appear that it simply installs everything into their target directories as dpkg would; so installing alongside the official xbps package file targets. I also don't think that's a good idea. 

What I think would be great is if instead of spitting out a full package, a parser like this generates a package template with the dependencies and other package info filled in, and leaves it to the maintainer to make whatever tweaks needed. A tool like that should be included.

Because it's for the most part individual applications you would have to install this way I believe that these packages should live in their own folders in /opt with a launch script placed in bin, which is currently what the bitwig package does. But it's worthwhile to have a larger conversation, because since this is a common enough use case it would be worthwhile to establish conventions about opt packages.