xfce/modules/trunk(-po): all core modules?!
stephan at xfce.org
Wed Nov 28 18:55:51 CET 2007
On Nov 28, 2007 12:27 PM, <mmassonnet at gmail.com> wrote:
> On Wed, Nov 28, 2007 at 12:19:14AM -0800, Brian J. Tarricone wrote:
> > On Wed, 28 Nov 2007 09:08:02 +0100 Stephan Arts wrote:
> > > On Nov 28, 2007 9:04 AM, Stephan Arts <stephan at xfce.org> wrote:
> > > > Hi,
> > > >
> > > > I was wondering, what is the policy regarding the
> > > > xfce/modules/trunk(-po) link in svn?
> > > >
> > > > Does it cover all 'core' components, or should it cover all trunk's
> > > > from every component inside the xfce repositories?
> > [...]
> > > > I imagine some of these components are outdated, depricated or
> > > > abandoned. Others are brand-new or experimental. But in any case, I
> > > > believe the xfce/modules/trunk(-po) links are a bit outdated, it
> > > > might be a good idea what to include and what to exclude from it.
> > >
> > > s/good idea/good idea to discuss/
> > I don't think this really needs much discussion: it appears to only be
> > useful for translators, so it should include whatever is useful for
> > translators.
> > It tends to fall out of sync with the actual modules present because
> > someone has to remember to update it. Feel free to do so yourself.
> > On the other hand, if a script didn't want to rely on those, they could
> > simply do something like this:
> > for module in `svn ls http://svn.xfce.org/svn/xfce/`; do
> > svn co http://svn.xfce.org/svn/xfce/$module/trunk/po $module-po
> > done
> > ... with something similar done for the branches. Modules that don't
> > have po dirs or don't have a trunk anymore will simply fail. Annoying
> > maintenance problem solved.
> That's no-no for the translator. He is going to translate everything,
> which covers more than the core components of Xfce, and waste time. The
> external svn links keep the list of components dynamic, e.g. there is no
> static list to update as it is the case currently for some scripts.
> For trunk-po, I would go for this list:
> - libexo
> - libxfce4menu
> - libxfce4util
> - libxfcegui4
> - mousepad
> - squeeze
> - terminal
> - thunar
> - xarchiver
> - xfburn
> - xfcalendar
> - xfce-mcs-manager
> - xfce-mcs-plugins
> - xfce-utils
> - xfce4-appfinder
> - xfce4-icon-theme
> - xfce4-mixer
> - xfce4-panel
> - xfce4-session
> - xfce4-terminal
> - xfdesktop
> - xfmedia
> - xfprint
> - xfwm4
> The rest has either nothing to translate or is outdated.
> You shouldn't wait to commit these changes, if you see that component
> foo is missing, you can add it afterwards. I did so on svn/goodies.
> Some random comments:
> - xfce4-trigger-launcher: panel plugin, move it over goodies?
> > -brian
Personally, I prefer the approach of keeping the modules/trunk(-po)
links up to date.
I'd love to do so myself, but someone should give me the
svn-permissions to do so.
More information about the Xfce4-dev