Change Details

I'm completely open to the bikeshedding process. The two concerns I'm aware of are - Where to put all the `.debug` files? The current approach creates multiple `.debug` directories, while @bapt suggested to use `${LOCALBASE}/lib/debug` to mirror `/usr/lib/debug`. I don't have a strong opinion here. - How to name the subpackage? I'm proposing `debuginfo` to underline the fact that the package installs only a debugging info files, not a debug flavor of the software itself. My shell skills are lacking, so there probably also a room for improvement.

I'm completely open to the bikeshedding process. The two concerns I'm aware of are - How to name the subpackage? I'm proposing `debuginfo` to underline the fact that the package installs only a debugging info files, not a debug flavor of the software itself. My shell skills are lacking, so there probably also a room for improvement.

I'm completely open to the bikeshedding process. The two concerns I'm aware of are - Where to put all the `.debug` files? The current approach creates multiple `.debug` directories, while @bapt suggested to use `${LOCALBASE}/lib/debug` to mirror `/usr/lib/debug`. I don't have a strong opinion here. - How to name the subpackage? I'm proposing `debuginfo` to underline the fact that the package installs only a debugging info files, not a debug flavor of the software itself. My shell skills are lacking, so there probably also a room for improvement.