Comment 26 for bug 738973

On 27/08/2012 20:49, Gellule wrote:
> By the way, I am getting a little lost with all the great feedback you're giving me.
> Could we open bug reports and somehow tag them so that they can be easily
> searched for? I can have a first pass at this if you wish.

Proposal: I will file new reports for issues as they occur with local packages based on the renewed blueprint, and tag them with 'gtk-osx' and 'packaging'. You can then search for them via 'Advanced Search' <https://bugs.launchpad.net/inkscape/+bugs?advanced=1>:
1) Scroll down on that page to 'Tags:',
2) enter both tags into the field,
3) check '[x] All' right below the 'Tags:' field
   (to only find reports which have both tags set)

We had used the tag 'gtk-osx' for all issues specific to build and runtime issues if Inkscape is built with the Quartz backend of GTK+ (irrespective of whether mac menu integration was used or not). Several of these reports are placeholders of upstream issues. The name 'gtk-osx' wasn't a good choice (now I know better and would have used 'gtk-quartz' instead), but at that time I was too focused to not have 'Aqua' sneak in into the tags ;) Changing all tags now doesn't make sense IMHO.

We could use a combination of tags for separate issues:
'gtk-osx' -> general category for issues with Inkscape using the Quartz backend of GTK+
'gtk-osx packaging' -> issues with application bundles created with gtk-mac-bundler
'gtk-osx desktop-integration' -> (future) issues with 'gtk-mac-integration / gtk-osx-application'