Re: metapackage for lokalize
On Thursday 09 July 2009 08:21:17 Nick Shaforostoff wrote: And your first commit looks good. One thing though, please add a changelog entry. I currently added a dummy entry for you ;) should I somehow communicate my changes to ubuntu? or they are on their own? I think they sync from time to time from us. /Sune -- Genius, I cannot turn on a wordprocessor from the control folder inside Windows NT, how does it work? You should never reinstall the CPU, so that from the file within ICQ you never have to telnet to the periferic to click with the 3D menu of the attachment. -- http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-talk
Re: metapackage for lokalize
On Sunday 12 July 2009 19:46:35 Sune Vuorela wrote: On Thursday 09 July 2009 08:21:17 Nick Shaforostoff wrote: And your first commit looks good. One thing though, please add a changelog entry. I currently added a dummy entry for you ;) should I somehow communicate my changes to ubuntu? or they are on their own? I think they sync from time to time from us. We (Kubuntu) do merge our packages with the Debian updates and make an effort to feed back useful changes to Debian once per 6 month release cycle. Sune did point these changes out to me on IRC and so I'll pull them from the Debian svn. Thanks for thinking of us. You are welcome to visit (#kubuntu-devel) on freenode anytime you wish to chat with us about anything Kubuntu specific. Thanks. Scott K -- http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-talk
metapackage for lokalize
Hi all. I'm developer of lokalize (kdesdk) and I've just been given access to pkg-kde repository. Lokalize massively extends its functionality via python scripts. And although it is still usable for some use cases w/o additional dependencies (gettext, python-kde4, translate-toolkit, python-lxml, python-dbus, subversion) which take quite a bit of disk space (over 30 MB), a newbie would be confused by missing features if they weren't installed. So my idea is to rename current lokalize package as it is to lokalize-core, and add a metapackage that would hard-depend on lokalize-core and all its additional dependencies. So that an experienced user still will have the choice of installing only stuff he wants. Am I allowed to do this in trunk (i.e. targeting for KDE 4.3) Is this the right way to do? Maybe adding a comment about recommended packages to package description is enough? -- http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-talk
Re: metapackage for lokalize
Nick Shaforostoff shaforost...@kde.ru writes: So my idea is to rename current lokalize package as it is to lokalize-core, and add a metapackage that would hard-depend on lokalize-core and all its additional dependencies. So that an experienced user still will have the choice of installing only stuff he wants. Am I allowed to do this in trunk (i.e. targeting for KDE 4.3) Is this the right way to do? Maybe adding a comment about recommended packages to package description is enough? Or to README.Debian. I believe this is exactly what Recommends are there for. Recommends are installed by default on standard setups and an experienced user can choose not to install them. Matthias -- http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-talk
