m not sure it is a big issue or no. Overall such changes will ease many things, so either we find a way to do the move smoothly (adding code to ensure smooth upgrade) or just break all and require a full reconfiguration (including moving plugins to new path), what do you think about ?
dufferzafar
having an INI file is defintely better than the registry, as it'll allow portability
zas
yes, and it eases multiple configs support (just pass config file path on command line ie.)
dufferzafar
i was going to ask about that
zas
i think the move is needed, but i'm not sure how and when
Freso
Is 1.3.0 going to be the next version number? If so, I think it'd be okay to do a full reconfig. Would allow to do a lot of things a lot cleaner with less code. Would be more of an annoyance to end users, but at least we won't suggest that things will go smoothly and then have to take the blame when everything explodes.
dufferzafar: One profile for "FLAC archive", one for "portale player .ogg collection", one for "media center", etc.
kepstin-laptop uses a patch that allows tagger script to read file paths and types, so his tagger script handles doing profiles automatically in a single picard config.
(I'm currently symlink juggling various profiles.)
zas
Mineo: no idea, perhaps they ends to be the same
Mineo
I don't think different configuration files are a good solution for providing tagging profiles
only very few users are going to create different shortcuts that start picard with different configs because no other application requires you to do that
kepstin-laptop
the only reason I'd use tagging profiles would be to have a profile that writes id3v2.3 tags for people using windows, while my normal stuff uses id3v2.4.
although our id3v2.3 support has improved to the point where I just leave thata enabled by default now :/
zas
Mineo: agreed, but if we use only config files it makes sense to provide a command line option to load a different one than the default one, also it will be handy for testing/debugging
Mineo
I agree that it's probably useful if you're testing stuff
yes, ofc but locations should be the same, API changed (perhaps a reason to use our own lib)
kepstin-laptop
we could always be really crazy and switch to pyqt5 at some point
hawke1 joined the channel
zas
anyway, whatever we use to get useful paths, i wonder if such move should pre or post next stable release
kepstin-laptop
hmm, the next stable release has been a fairly long time coming, and already has a bunch of new features. I think making a big change like this should happen after the release.
that would give us more time to figure out how to make upgrades and stuff work cleanly, too.
zas
i tend to agree, i think we'll not have OAuth in the next stable release, so may be we can have another stable release with fewer minor changes and 2-3 major changes before next year (including new file paths, better upgrade/downgrade paths, OAuth and plugin interface from https://github.com/musicbrainz/picard/pull/334)
misterswag joined the channel
hawke1 joined the channel
adhawkins-away joined the channel
kepstin_ joined the channel
demonimin joined the channel
nikki
Gentlecat: thanks :)
Gentlecat
:)
sampsyo joined the channel
hawke1 joined the channel
aandre joined the channel
aandre has left the channel
Freso
zas: You could come to the Summit next month and we could make a Picard release during that, so we could have a Picard release party and all. ;D
gcw_ joined the channel
gcw_
Hi all, X-post from #musicbrainz: I'm installing musicbrainz-server on OSX mavericks but getting an error when trying to make postgresql-musicbrainz-collate. Specifically, the include of unicode/utypes.h isn't found.
I have libicu installed via homebrew, and specifying the include directory when running make still doesn't find it, so looking for advice
kepstin
hmm. that should be provided by ICU...
OSX isn't really a supported platform tho
gcw_
Ya, I mean as far as I can tell everything has been working in the install process, just an include issue :/
kepstin
how did you try specifying the include directory?
and also, can you run the 'icu-config' tool in your terminal?
gcw_
cmd used is make -I /usr/local/opt/icu4c/include
kepstin
yeah, that wouldn't actually do anything.
that specifies the makefile include directory, not the compiler include directory :)
Just to confirm - can your run 'icu-config' in the terminal?