Hi @juliank,
I'm revisiting packaging these tools and I wanted to confirm if we
should do these separately or not.
Personally I think it makes sense to create two separate packages, even
if they are very small applications and follow a similar/identical
release cadence, as they have two distinct source trees and don't share
any components at all. As Talha mentioned they're also very different in
their purpose and use cases, even if they seem similar.
Is there any prior work/other packages to base the decision on combining
the packages on? I can understand wanting to reduce the maintenance
burden, but they are distinctly different tools.
** Changed in: ubuntu
Assignee: Talha Can Havadar (tchavadar) => Isaac True (itrue)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067254
Title:
[needs-packaging] amd-qos package from AMD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2067254/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
