Re: oxygen icons moved
On Sat, Mar 28, 2009, Andreas Pakulat wrote: - some application developers don't want to assume that KDE4 shipping those newly added application icons is installed on user machine, so just in any case they ship icons themselves. Thats a moot point, any KDE app has kdebase/runtime as runtime dependency so oxygen icons are _always_ there. It's moot, because you missed the point :) Lets say application A need icons cool_icon, which will only be available in KDE4.3, but application A is released before KDE4.3, solution for developers of application A: ship cool_icon and (forget to) remove it when 4.3 is available and becomes a required dependency for application A. -- Cyrille Berger ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: oxygen icons moved
Alle sabato 28 marzo 2009, Cyrille Berger ha scritto: Lets say application A need icons cool_icon, which will only be available in KDE4.3, but application A is released before KDE4.3, solution for developers of application A: ship cool_icon and (forget to) remove it when 4.3 is available and becomes a required dependency for application A. That is perfectly fine, as long as (as written in my other email) the versions installed by the application are provided a) locally in the application datadir b) in the hicolour namespace This way, when the icon theme will provide the cool_icon (installed globally) needed by the application, it will override (as in runtime loading of the icon, not as in file overwriting) the local application version. -- Pino Toscano signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: oxygen icons moved
Hi, Exactly, that's actually the reason, why in Gentoo, we get some number of duplicated icons causing file collisions that need to be handled. Of course, usually after some time, they are eventually removed from those packages. Some applications still ship some icons on their own (I could give some examples, like digikam, and used to - koffice). The possible reasons are: - some application developers don't know whether some icon is shipped already with KDE4 - some application developers don't want to assume that KDE4 shipping those newly added application icons is installed on user machine, so just in any case they ship icons themselves. Neither of the two. The *real* reasons for clashes between an icon installed with an icon theme and one installed with an application itself is just one: an application polluting the namespace of the global icon theme. Back to your digikam issue: this was actually an issue because they used to install the application icon within the oxygen icon theme... and that same icon was put in the trunk version of oxygen. The *only* sane way to resolve these issues is having applications install their icons within the hicolour namespace, with: - icons for the application (say, the one for representing it, usually in the 'apps' category) in the global icon theme (usually /usr/share/icons/hicolor) - other application icons within the local datadir of the application ($datadir/appname/icons/) This ensures some things: - private icons for an applications stay really private - as hicolour is the low-level denominator for icon themes, if you use any icon theme different than oxygen you can actually see application icon in the menu (either kde's or gnome's or any other xdg-menu implementation) - a better version of some icon (either the icon of an application icon or some private application one) provided globally in an icon theme will override the hicolor one (as expected) so that in effect every Oxygen icon create is in kdesupport/oxygen-icons) ... minus icons of applications (ie those in the 'apps' category) for applications which have no own hicolor version. As said above, any application should carry its own icon with the hicolor icon theme, otherwise there will be an happy question mark when being used in non-oxygen contexts (eg in a gnome menu). -- Pino Toscano signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: oxygen icons moved
On Saturday 28 March 2009, Pino Toscano wrote: That is perfectly fine, as long as (as written in my other email) the versions installed by the application are provided a) locally in the application datadir b) in the hicolour namespace This way, when the icon theme will provide the cool_icon (installed globally) needed by the application, it will override (as in runtime loading of the icon, not as in file overwriting) the local application version. That doesn't solve the problem of icons beeing spread everywhere :) -- Cyrille Berger ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: oxygen icons moved
On Thursday 26 March 2009 16:00:22 Dirk Mueller wrote: On Thursday 19 March 2009, Cyrille Berger wrote: I talked with Casper (over irc) on what would be needed for releasing oxygen icons. Unless I missed something, it's tag, export and upload (mail kde- packager ?), and he seemed ready to do it himself. I'm willing to do the packaging myself, but I need the information where to find the oxygen icons for KDE 4.2.2. You're not really telling me that I should use the trunk version of oxygen icons, right? What is the version number of the oxygen icons? where can I find the version that matches KDE 4.2 branch? Ok, I didn't talk with Casper or Nuno here, so take my word with a grain of salt here, but... why not? It's icons, we shouldn't have any regressions, and we have decided to split the release exactly to provide the most fresh icons possible. But then, I'm not sure if we want to break packaging scripts in a minor release. Bye, -Riccardo -- GPG key: 3D0F6376 When encrypting, please encrypt also for this subkey: 9EBD7FE1 - Pace Peace Paix Paz Frieden Pax Pokój Friður Fred Béke 和平 Hasiti Lapé Hetep Malu Mир Wolakota Santiphap Irini Peoch שלום Shanti Vrede Baris Rój Mír Taika Rongo Sulh Mir Py'guapy 평화 ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: oxygen icons moved
On 27.03.09 10:05:11, Riccardo Iaconelli wrote: On Thursday 26 March 2009 16:00:22 Dirk Mueller wrote: On Thursday 19 March 2009, Cyrille Berger wrote: I talked with Casper (over irc) on what would be needed for releasing oxygen icons. Unless I missed something, it's tag, export and upload (mail kde- packager ?), and he seemed ready to do it himself. I'm willing to do the packaging myself, but I need the information where to find the oxygen icons for KDE 4.2.2. You're not really telling me that I should use the trunk version of oxygen icons, right? What is the version number of the oxygen icons? where can I find the version that matches KDE 4.2 branch? Ok, I didn't talk with Casper or Nuno here, so take my word with a grain of salt here, but... why not? Because you're sometimes changing names of icons and that breaks existing code - unless you backport the code-changes before the release. Andreas -- Try to get all of your posthumous medals in advance. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: oxygen icons moved
On Friday 27 March 2009 10:05:11 Riccardo Iaconelli wrote: On Thursday 26 March 2009 16:00:22 Dirk Mueller wrote: On Thursday 19 March 2009, Cyrille Berger wrote: I talked with Casper (over irc) on what would be needed for releasing oxygen icons. Unless I missed something, it's tag, export and upload (mail kde- packager ?), and he seemed ready to do it himself. I'm willing to do the packaging myself, but I need the information where to find the oxygen icons for KDE 4.2.2. You're not really telling me that I should use the trunk version of oxygen icons, right? What is the version number of the oxygen icons? where can I find the version that matches KDE 4.2 branch? Ok, I didn't talk with Casper or Nuno here, so take my word with a grain of salt here, but... why not? It's icons, we shouldn't have any regressions, and we have decided to split the release exactly to provide the most fresh icons possible. But then, I'm not sure if we want to break packaging scripts in a minor release. I think removing the icons from branch and shipping them from kdesupport is a bad idea. With this kind of structural changes to a stable branch, we're making it harder for packagers to ship our updates and bugfixes, they're now either stuck with putting the icons back into the old location and ship this, or offer the icons as separate package, which creates more work for these poor people. Shipping Oxygen separately might be interesting for third party applications to use the icons, the names are standardized and they don't depend on neither KDE nor Qt (in fact they depend on being rendered with Inkscape ;)). We need to consider that Oxygen is part of a stable platform. Even if we fix the apps that we ship together with Oxygen, that still means that we might screw some third party apps that suddenly loose icons in a x.y.z bugfix and translation update. It's fine to update the Oxygen icons also in a stable cycle, the large majority of the updates to Oxygen is probably a 100% safe to backport. For trunk, we can make these changes, but we need to consider the above points just as well. Backwards compatibility is just as important across major cycles (4.2 - 4.3) releases. I don't really see why putting Oxygen into kdesupport would mean that users get updates more often. I think it'll work the other way, branch is shipped every month, that means improvements to Oxygen can be shipped to the user usually in less than four weeks. By putting in them kdesupport (which is less visible and might not be updated by packagers along with a x.y.z release) the likely effect is that Oxygen is overall updated *less* often. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: oxygen icons moved
A Friday 27 March 2009 23:49:32, Sebastian Kügler escreveu: On Friday 27 March 2009 10:05:11 Riccardo Iaconelli wrote: On Thursday 26 March 2009 16:00:22 Dirk Mueller wrote: On Thursday 19 March 2009, Cyrille Berger wrote: I talked with Casper (over irc) on what would be needed for releasing oxygen icons. Unless I missed something, it's tag, export and upload (mail kde- packager ?), and he seemed ready to do it himself. I'm willing to do the packaging myself, but I need the information where to find the oxygen icons for KDE 4.2.2. You're not really telling me that I should use the trunk version of oxygen icons, right? What is the version number of the oxygen icons? where can I find the version that matches KDE 4.2 branch? Ok, I didn't talk with Casper or Nuno here, so take my word with a grain of salt here, but... why not? It's icons, we shouldn't have any regressions, and we have decided to split the release exactly to provide the most fresh icons possible. But then, I'm not sure if we want to break packaging scripts in a minor release. I think removing the icons from branch and shipping them from kdesupport is a bad idea. With this kind of structural changes to a stable branch, we're making it harder for packagers to ship our updates and bugfixes, they're now either stuck with putting the icons back into the old location and ship this, or offer the icons as separate package, which creates more work for these poor people. Shipping Oxygen separately might be interesting for third party applications to use the icons, the names are standardized and they don't depend on neither KDE nor Qt (in fact they depend on being rendered with Inkscape ;)). We need to consider that Oxygen is part of a stable platform. Even if we fix the apps that we ship together with Oxygen, that still means that we might screw some third party apps that suddenly loose icons in a x.y.z bugfix and translation update. It's fine to update the Oxygen icons also in a stable cycle, the large majority of the updates to Oxygen is probably a 100% safe to backport. For trunk, we can make these changes, but we need to consider the above points just as well. Backwards compatibility is just as important across major cycles (4.2 - 4.3) releases. I don't really see why putting Oxygen into kdesupport would mean that users get updates more often. I think it'll work the other way, branch is shipped every month, that means improvements to Oxygen can be shipped to the user usually in less than four weeks. By putting in them kdesupport (which is less visible and might not be updated by packagers along with a x.y.z release) the likely effect is that Oxygen is overall updated *less* often. Well my issue is another as nothing to do with the issues so far. its about control, we are creating a new kde3.x mess couse aplications are creating their hown versions of the same icons, and not teling any one they do so, couse well they dont have 2. second i have alrady done a couple of duplicated icons with slightly difrent names couse well i forgot i did icon a for app B and icon c for app D and a=c just that they dont. i have no idea of how many icons we have done so far no idea of what apps are using couse its out of the oxygen directory its scatered all around kde svn. this is a solution to that issue, no one came up with a beter one.. -- Oxygen coordinator ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: oxygen icons moved
A Friday 27 March 2009 23:49:32, Sebastian Kügler escreveu: I don't really see why putting Oxygen into kdesupport would mean that users get updates more often. I think it'll work the other way, branch is shipped every month, that means improvements to Oxygen can be shipped to the user usually in less than four weeks. By putting in them kdesupport (which is less visible and might not be updated by packagers along with a x.y.z release) the likely effect is that Oxygen is overall updated *less* often. I guess it's not the case here, as distributions usually follow weekly unstable snapshots as well, so it's very unlikely they will miss Oxygen icons release. On Saturday 28 of March 2009 01:27:58 Nuno Pinheiro wrote: Well my issue is another as nothing to do with the issues so far. its about control, we are creating a new kde3.x mess couse aplications are creating their hown versions of the same icons, and not teling any one they do so, couse well they dont have 2. second i have alrady done a couple of duplicated icons with slightly difrent names couse well i forgot i did icon a for app B and icon c for app D and a=c just that they dont. i have no idea of how many icons we have done so far no idea of what apps are using couse its out of the oxygen directory its scatered all around kde svn. Exactly, that's actually the reason, why in Gentoo, we get some number of duplicated icons causing file collisions that need to be handled. Of course, usually after some time, they are eventually removed from those packages. Some applications still ship some icons on their own (I could give some examples, like digikam, and used to - koffice). The possible reasons are: - some application developers don't know whether some icon is shipped already with KDE4 - some application developers don't want to assume that KDE4 shipping those newly added application icons is installed on user machine, so just in any case they ship icons themselves. The idea, of frequent updates to Oxygen icons in kdesupport (and frequent releases) - will work and will give this control over icon distribution - provided backward compatibility issues with 4.2.x and 4.3.x regarding icons are resolved, and provided 3rd party (extragear/plasma and other as well) KDE application developers will respect that way of distributing them. (in short, any icon missing or report about icon being duplicated - contact Oxygen team - icon set updated and released in weekly manner as usual or sth like this - so that in effect every Oxygen icon create is in kdesupport/oxygen-icons) -- regards MM signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: oxygen icons moved
A Friday 27 March 2009 23:49:32, Sebastian Kügler escreveu: I don't really see why putting Oxygen into kdesupport would mean that users get updates more often. I think it'll work the other way, branch is shipped every month, that means improvements to Oxygen can be shipped to the user usually in less than four weeks. By putting in them kdesupport (which is less visible and might not be updated by packagers along with a x.y.z release) the likely effect is that Oxygen is overall updated *less* often. And KDE packagers could use the same weekly manner of automatic packaging oxygen icons along with unstable (SVN) snapshots (so called 4.2.67 etc) -- regards MM signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: oxygen icons moved
On Saturday 28 March 2009 01:27:58 Nuno Pinheiro wrote: Well my issue is another as nothing to do with the issues so far. its about control, we are creating a new kde3.x mess couse aplications are creating their hown versions of the same icons, and not teling any one they do so, couse well they dont have 2. I see. I don't see another solution than to make it easy to ship all icons from one canonical source. Maybe we should have a mechanism to download missing icons automatically, so Oxygen is shipped as webservice. Or at least educating application developers better. Realistically, there will always be the problem of people not passing their modifications up, it's just too easy to change the name and ship it, while passing it back upstream is hard. This doesn't mean that what Oxygen ships should be clean. Am I assuming correctly that the only regressions caused by icons is when an icon gets a different name and needs to be moved? second i have alrady done a couple of duplicated icons with slightly difrent names couse well i forgot i did icon a for app B and icon c for app D and a=c just that they dont. i have no idea of how many icons we have done so far no idea of what apps are using couse its out of the oxygen directory its scatered all around kde svn. That sucks :/. So to you as icon developer, there should be One Canonical Place To Put All Icons... this is a solution to that issue, no one came up with a beter one.. Let's try to find a better one then :) I don't see in how far putting icons into kdesupport would solve that problem? Or is the problem the size of Oxygen? I can imagine that you don't want to ship every single special application icon in the world in the kdebase tarball. In that case, it would make sense to ship it separately. This change (which is the point of this discussion) is made already. Still, that's not something we should change in a bug fix update as Andreas pointed out as well. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: oxygen icons moved
A Saturday 28 March 2009 00:55:32, Sebastian Kügler escreveu: On Saturday 28 March 2009 01:27:58 Nuno Pinheiro wrote: Well my issue is another as nothing to do with the issues so far. its about control, we are creating a new kde3.x mess couse aplications are creating their hown versions of the same icons, and not teling any one they do so, couse well they dont have 2. I see. I don't see another solution than to make it easy to ship all icons from one canonical source. Maybe we should have a mechanism to download missing icons automatically, so Oxygen is shipped as webservice. Or at least educating application developers better. Realistically, there will always be the problem of people not passing their modifications up, it's just too easy to change the name and ship it, while passing it back upstream is hard. This doesn't mean that what Oxygen ships should be clean. Am I assuming correctly that the only regressions caused by icons is when an icon gets a different name and needs to be moved? second i have alrady done a couple of duplicated icons with slightly difrent names couse well i forgot i did icon a for app B and icon c for app D and a=c just that they dont. i have no idea of how many icons we have done so far no idea of what apps are using couse its out of the oxygen directory its scatered all around kde svn. That sucks :/. So to you as icon developer, there should be One Canonical Place To Put All Icons... yeap this is a solution to that issue, no one came up with a beter one.. Let's try to find a better one then :) I don't see in how far putting icons into kdesupport would solve that problem? the idea was to put every single icon there Or is the problem the size of Oxygen? I can imagine that you don't want to ship every single special application icon in the world in the kdebase tarball. yeap in the end it will be quite a large group it allready is and im gessing about arround 100 are outside already, In that case, it would make sense to ship it separately. This change (which is the point of this discussion) is made already. Still, that's not something we should change in a bug fix update as Andreas pointed out as well. Realy im fine with anything as long as it works, by working i meen having some way of geting a complete overview of the intire icon set, with i dont right now, and nor do developers, a developer serching for an specific icon for his app as no place to go and look for all of them unless he instales every single app out there that ships oxygen icons, and heven if he does he cant be sure its realy an oxygen icon or a icon some application developer found some ware and put it in his install oxygen directory... I have no perfect anser for this but I can complain about it I have spoken about this to the other icon designers we all agrea that a centralized place for all icons is beter... -- Oxygen coordinator ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: oxygen icons moved
On 28.03.09 01:47:23, Maciej Mrozowski wrote: A Friday 27 March 2009 23:49:32, Sebastian Kügler escreveu: Some applications still ship some icons on their own (I could give some examples, like digikam, and used to - koffice). The possible reasons are: - some application developers don't know whether some icon is shipped already with KDE4 Then they should start to look at the icons in kdebase/runtime (or now oxygen-icons in kdesupport). An app developer should at least coordinate these things somewhat with the artists, unless they want to ship their own iconset. - some application developers don't want to assume that KDE4 shipping those newly added application icons is installed on user machine, so just in any case they ship icons themselves. Thats a moot point, any KDE app has kdebase/runtime as runtime dependency so oxygen icons are _always_ there. Andreas -- You may worry about your hair-do today, but tomorrow much peanut butter will be sold. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: oxygen icons moved
On Saturday 28 March 2009 02:26:26 Nuno Pinheiro wrote: A Saturday 28 March 2009 00:55:32, Sebastian Kügler escreveu: the idea was to put every single icon there Or is the problem the size of Oxygen? I can imagine that you don't want to ship every single special application icon in the world in the kdebase tarball. yeap in the end it will be quite a large group it allready is and im gessing about arround 100 are outside already, In that case, it would make sense to ship it separately. This change (which is the point of this discussion) is made already. Still, that's not something we should change in a bug fix update as Andreas pointed out as well. Realy im fine with anything as long as it works, by working i meen having some way of geting a complete overview of the intire icon set, with i dont right now, and nor do developers, a developer serching for an specific icon for his app as no place to go and look for all of them unless he instales every single app out there that ships oxygen icons, and heven if he does he cant be sure its realy an oxygen icon or a icon some application developer found some ware and put it in his install oxygen directory... That makes sense. So for the future, we'll ship Oxygen separately. That shaves of quite some MBs from the kdebase tarball (you mentioned 20K files), makes it easier to maintain for you and keep in a sane state for others to work with. How should those releases be shipped? Is it simply OK to grab a snapshot from kdesupport anytime? Otherwise, tags would need to be created for the snapshot release revisions. I have no perfect anser for this but I can complain about it I have spoken about this to the other icon designers we all agrea that a centralized place for all icons is beter... Then the solution to this is to do with KDE 4.2.2 whatever Dirk thinks it's sensible (I can imagine that it's really way to late to change this for 4.2.2.) For trunk we'll keep the separate Oxygen in kdesupport anyway. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: oxygen icons moved
On 28.03.09 01:55:32, Sebastian Kügler wrote: On Saturday 28 March 2009 01:27:58 Nuno Pinheiro wrote: Well my issue is another as nothing to do with the issues so far. its about control, we are creating a new kde3.x mess couse aplications are creating their hown versions of the same icons, and not teling any one they do so, couse well they dont have 2. I see. I don't see another solution than to make it easy to ship all icons from one canonical source. Maybe we should have a mechanism to download missing icons automatically, so Oxygen is shipped as webservice. Or at least educating application developers better. Realistically, there will always be the problem of people not passing their modifications up, it's just too easy to change the name and ship it, while passing it back upstream is hard. Another reason to ship icons with an application is that there's only a limited amount of artists available and they have only limited time. In KDevelop we have currently two icons copied from an oxygen icon (and one coming from KDE3) that we ship, simply because the artists didn't yet get around to work on the list of icons posted in the wiki for KDevelop. I'm trying to keep such things out of kdevelop and thats why there are no icons in the menus for some of the most-used actions, but in some cases having text is simply not an option (toolbars in dockwidgets for example). Am I assuming correctly that the only regressions caused by icons is when an icon gets a different name and needs to be moved? Yes in that case we'd either need a copy of the old name still around or make sure all apps using the icon are updated. this is a solution to that issue, no one came up with a beter one.. Let's try to find a better one then :) I don't see in how far putting icons into kdesupport would solve that problem? Yeah, I think the problem is rather that a) app devs don't know that kdebase/runtime is a dependency for _every_ kde app and they might also not know they should pick icons from there or request them from the oxygen tema b) what I said above about limited resources for creating icons Or is the problem the size of Oxygen? I can imagine that you don't want to ship every single special application icon in the world in the kdebase tarball. In that case, it would make sense to ship it separately. I don't really see how shipping a huge tarball that all kde apps depend on outside of kdebase is better than shipping it inside. But I don't have a good idea how to fix the size of the oxygen dir (in terms of files) without starting to scatter around app-specific icons to the applications - which might again lead to duplication and confusion as Nuno pointed out. Andreas -- You're ugly and your mother dresses you funny. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: oxygen icons moved
On 28.03.09 01:26:26, Nuno Pinheiro wrote: A Saturday 28 March 2009 00:55:32, Sebastian Kügler escreveu: In that case, it would make sense to ship it separately. This change (which is the point of this discussion) is made already. Still, that's not something we should change in a bug fix update as Andreas pointed out as well. Realy im fine with anything as long as it works, by working i meen having some way of geting a complete overview of the intire icon set, with i dont right now, and nor do developers, I can only speak for myself, but I as a developer always use kdebase/runtime/oxygen to get an overview over icons that I should use and to find one when I have a certain action. a developer serching for an specific icon for his app as no place to go and look for all of them unless he instales every single app out there that ships oxygen icons, and heven if he does he cant be sure its realy an oxygen icon or a icon some application developer found some ware and put it in his install oxygen directory... Hmm, I'm not a guru in the icon-spec, but shouldn't apps install their custom icons not into the oxygen directory but rather into the fallback hicolor or what it is called? At least thats what KDevelop does with the three custom icons it has and that gives other developers a clear hint that these icons are not part of the oxygen iconset. (I just see that we're creating quite some mess actually in kdevelop/pics, I'll try to fix that tomorrow). I have no perfect anser for this but I can complain about it I have spoken about this to the other icon designers we all agrea that a centralized place for all icons is beter... I don't see why that centralized place cannot be kdebase/runtime as that is already a hard runtime requirement for all kde apps. I do understand that you could more easily produce releases yourself from a kdesupport/oxygen-icons module, so I'm not saying you should go back to kdebase/runtime if the separate releases are an important factor. Apart from that I mostly see education problems and the problem of people copying existing apps to start their own (and existing apps doing it wrong). And you can't fix those problems with throwing software or hardware at them, btw. anybody knows what the tutorials on techbase tell people about icons? Andreas -- Beauty and harmony are as necessary to you as the very breath of life. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: oxygen icons moved
On Thursday 19 March 2009, Cyrille Berger wrote: I talked with Casper (over irc) on what would be needed for releasing oxygen icons. Unless I missed something, it's tag, export and upload (mail kde- packager ?), and he seemed ready to do it himself. I'm willing to do the packaging myself, but I need the information where to find the oxygen icons for KDE 4.2.2. You're not really telling me that I should use the trunk version of oxygen icons, right? What is the version number of the oxygen icons? where can I find the version that matches KDE 4.2 branch? Thanks, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: oxygen icons moved
On Monday 16 March 2009, C. Boemann wrote: The oxygen icons have been moved to kdesupport/oxygenicons The intension is to release it more often than kde itself, so that we can provide up-to-date icons for applications that are outside the normal KDE release schedules I am probably missing the discussion somewhere.. but who is going to provide working oxygen tarballs for each KDE release and where are they being found? thanks, dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: oxygen icons moved
Dirk Mueller wrote: On Monday 16 March 2009, C. Boemann wrote: The oxygen icons have been moved to kdesupport/oxygenicons The intension is to release it more often than kde itself, so that we can provide up-to-date icons for applications that are outside the normal KDE release schedules I am probably missing the discussion somewhere.. but who is going to provide working oxygen tarballs for each KDE release and where are they being found? I'd go a step further, and highly recommend that oxygen make a standalone release (tarball) for public consumption asap, so that distros can get a head start on packaging it. -- Rex ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: oxygen icons moved
On Wednesday 18 March 2009, Allen Winter wrote: On Wednesday 18 March 2009 7:04:19 am Dirk Mueller wrote: I am probably missing the discussion somewhere.. but who is going to provide working oxygen tarballs for each KDE release and where are they being found? Dirk, The original thread subject was Fwd: icon packaging. I asked the same question in that thread. The relevant exchange follows: === Are you planning to manage the weekly snapshots yourself? Or do you expect Dirk to manage that? I was hoping I could be automated along with the snapshots. But no I wasn't prepared to do it myself, but if needed I can't be that difficult to blog-advertice for a person to do that. Well snapshots are themselves different from releases anyways, unless this is to be the idea of the oxygen icon release. And it looks to me like no one is doing it since unless the aforementioned blog advertisement has already been made and I missed it. Regards, - Michael Pyne signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
oxygen icons moved
The oxygen icons have been moved to kdesupport/oxygenicons The intension is to release it more often than kde itself, so that we can provide up-to-date icons for applications that are outside the normal KDE release schedules The oxygen icons will be removed from upcoming 4.2.2 kdebase too, Best regards Casper ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
