|Summary:||media-sound/laditools - Control and monitor a LADI system the easy way.|
|Product:||Gentoo Linux||Reporter:||tokiclover <tokiclover>|
|Component:||New packages||Assignee:||Default Assignee for New Packages <maintainer-wanted>|
|Severity:||enhancement||CC:||kripton, proaudio, tomwij, yngwin|
|Package list:||Runtime testing required:||---|
|Bug Depends on:||559242|
Description tokiclover 2012-11-12 21:56:42 UTC
Created attachment 329410 [details] media-sound/laditools-9999.ebuild This package is very handy for JACK users. Some are using some old apps that are not that compatible with the new JACK[dbus] trasition, but using laditools applet is more than usefull. Because the ladish package will provide a nice way with DBus to manage JACK connections/buses while laditools will configure JACK a very readable way.
Comment 1 tokiclover 2012-11-12 21:57:14 UTC
Created attachment 329412 [details] media-sound/laditools-1.0.1.ebuild
Comment 2 tokiclover 2012-11-12 21:57:43 UTC
Created attachment 329414 [details] media-sound/laditools-1.0_rc1.ebuild
Comment 3 tokiclover 2012-11-12 21:58:11 UTC
Created attachment 329416 [details] media-sound/Manifest
Comment 4 tokiclover 2012-11-12 21:58:54 UTC
Created attachment 329418 [details] media-sound/laditools/metadata.xml
Comment 5 tokiclover 2012-11-12 21:59:48 UTC
Created attachment 329420 [details] media-sound/laditools/files/laditools-1.0_rc1-no_extra_docs.patch
Comment 6 tokiclover 2012-11-12 22:02:11 UTC
Even if when laditools was undertaken by UbuntuOS, the tools remain usable with gtk+:3. It is perfectly working on my gtk+:2 based DE with a nice icon on my systray. The 1.0[.1] offers some extra menu to load save ladish or lash session easily.
Comment 7 tokiclover 2012-11-12 22:27:04 UTC
As for bug #442916, everything is on my overlay: https://github.com/tokiclover/bar-overlay. So no updates as everything should be working as expected for now.
Comment 8 Tom Wijsman (TomWij) (RETIRED) 2012-11-12 22:37:55 UTC
Under "Completing the bug form" at http://www.gentoo.org/doc/en/ebuild-submit.xml#doc_chap2 it reads: > The Severity field should be set to enhancement. This rule is in place so that new ebuilds don't get in the way of bugs to existing ebuilds, it also ensures maintainers looking for new ebuilds see your ebuild if they filter normal and higher. Please leave this in place unless you have a endorsed reason to do so...