After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 351340 - Port sound-juicer to use the single-instance application library
Port sound-juicer to use the single-instance application library
Status: RESOLVED DUPLICATE of bug 661363
Product: sound-juicer
Classification: Applications
Component: general
git master
Other All
: Normal enhancement
: ---
Assigned To: Sound Juicer Maintainers
Sound Juicer Maintainers
Depends on:
Blocks: 351092
 
 
Reported: 2006-08-14 18:56 UTC by Vytas
Modified: 2014-02-14 13:49 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement

Attachments
sound-juicer-2.14.4.diff (6.37 KB, patch)
2006-08-14 18:57 UTC, Vytas 		none Details | Review

Description Vytas 2006-08-14 18:56:07 UTC 
I have ported gnome-system-monitor and attach the patch below. One would also
need to copy libguniqueapp code to the gnome-system-monitor directory, changing
@GTK_CFLAGS@ to @UI_CFLAGS@ etc. I have produced a small tarball, which is
ready to drop in for testing:
http://guniqueapp.akl.lt/patches/libguniqueapp-0.4-for-sj.tar.bz2

Note: I have patched sound juicer 2.14.4, and some patches (mostly Makefile.am's) do not apply against current CVS version, but these are Makefile.am patches, sj-main.c is ok
Comment 1 Vytas 2006-08-14 18:57:57 UTC 
Created attachment 70881 [details] [review]
sound-juicer-2.14.4.diff

Typo in previous comment, left "gnome-system-monitor" instead of sound-juicer ;-)
Comment 2 Ross Burton 2007-03-26 13:31:46 UTC 
Comment on attachment 70881 [details] [review]
sound-juicer-2.14.4.diff

Now that GtkUnique is heading into GTK+ itself, this patch should be re-worked to use that (probably by having an optional dependency on the standalone version of the library).
Comment 3 Christophe Fergeau 2014-02-14 13:49:50 UTC 

*** This bug has been marked as a duplicate of bug 661363 ***