/srv/irclogs.ubuntu.com/2011/12/15/#ubuntustudio-devel.txt

ScottLmicahg, i am presuming that at some point i will need to add "Conflicts: ..." into the new ubuntustudio packages to keep from pulling in some of the older and now unused packages02:00
ScottLfor example, ubuntustudio-theme will no longer be needed, or ubuntustudio-menu, or ubuntustudio-icon-theme, etc02:01
micahgright, conflicts unless you're using transitional packages (which might help for LTS -> LTS upgrades if you support them or upgrades in general)02:09
micahgif you're using transitional packages, you'll want a versioned breaks/replaces when you switch to the transitional package02:09
ScottLby the way, i will be using your suggestion about including nautilus and thunar together for the time being02:44
ScottLi'm not sure i am get my head around how to do the transitional package correctly right now02:45
ScottLi'm not a fan of upgrades in general, especially for LTS -> LTS as they alway seems problematic02:51
ScottLhowever, that doesn't mean we shouldn't try to accommodate them02:52
ScottLmicahg, i am familiar with transitional packages, i did one for transitioning from audio seed to audio-common, audio-generation, and audio-recording02:53
ScottLbut i would appreciate a quick overview on what i might need to do02:53
ScottLi would presume that i need to make updates for the current packages that will no longer be needed, but make them depend on the new packages02:53
ScottLwhich will be a little weird as something like six packages are resolved into two packages now and i'm not exactly sure how that will be structured02:54
ScottLi'm also going to be a little unsure about the versioned breaks/replaces at this point02:55
ScottLlet me finish mapping the changes as they are now and then i should have a better feeling about this02:55
micahgScottL: the transitional packages are just binary entries in debian/control in the source that's taking over02:55
ScottLmicahg, but is it using the same binary name as the old, deprecated binaries?02:57
micahgyes, that's how it's transitional02:58
ScottLright02:58
ScottLbut with a newer version02:58
micahgwell, versions usually come from the source package02:58
ScottLoh, yeah03:43
ScottLbut won't this be kinda weird?  some of the current packages aren't aligned with version numbers03:43
ScottLi know that one of the currently used packages is at something like version 40, but the rest are at versions like 0.2003:44
ScottLwhen i do my final mapping of packages and functions i'll include version numbers too03:44
micahgScottL: in that case, Conflicts/Replaces might be fine, let's see what the various upgrade paths are, then we can decide04:03

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!