Ghee: > This is a good move! A couple of questions: > - Does this need to be arced?
Probably not, unless moving libsexy into spec-files and making the notification-daemon depend on it exposes new interfaces to end users. If this is just a change in the internal JDS private interfaces, there is no need to mention to ARC. > - Now that we have a complete list of packages, ie.e. same as the rest > of the community, should we use a separate package name instead of > tagging onto gnome-panel? If I remember correctly, the GNOME community has been talking about eventually merging libsexy into GTK+ or some other base library. If libsexy will be a temporary library, it probably makes more sense to "hide" it in a package like the panel or base-libs package rather than making it more visible with a separate package. Just my opinion, though. Brian > Jedy Wang wrote: >> Hi, >> >> Currently, libsexy is in spec-files-other and all applications >> dependes on it are in spec-files-other too. But actually >> notification-daemon(in SUNWgnome-panel.spec) depends on libsexy too >> but the dependency is removed by a internal patch. This disables the >> support of sexy-url-label in notification-daemon. Now I propose to >> move libsexy from spec-files-other to spec-files to enable this >> feature and remove the patch we maintained internal. Attached is the >> patch to move libsexy fomr spec-files-other to spec-files, remove the >> internal patch and add the dependency to libsexy into SUNWgnome-panel. >> >> Regards, >> >> Jedy >
