On Friday 25 August 2006 11:23, Fathi Boudra wrote:> Author: fboudra-guest > Date: 2006-08-25 09:23:38 +0000 (Fri, 25 Aug 2006) > New Revision: 4397 > > Modified: > kde-extras/kile/trunk/debian/changelog > kde-extras/kile/trunk/debian/kile.install > Log: > Move bibtex.xml and latex.xml from kdelibs-data to kile packageEverything IMHO of course: I don''t like this change (and some kate but not kile latex user here will agree). The highlighing should be available as soon as when kate(part) is installed. Not only when kile is installed. I would suggest to update kdelibs-data in case the kile one are more recent. *Or we somehow organize a *data-extra pkg. AFAIR these problems occured already several times with mimetype defs too :( ) Would be best kile upstream adds their higlighing in KDE branch so branch pulls would fix it. Or one of the team does the sync ;) Achim> > Modified: kde-extras/kile/trunk/debian/changelog > ==================================================================> --- kde-extras/kile/trunk/debian/changelog 2006-08-25 09:23:25 UTC (rev 4396) > +++ kde-extras/kile/trunk/debian/changelog 2006-08-25 09:23:38 UTC (rev 4397) > @@ -1,7 +1,10 @@ > kile (1:1.9.2-1) unstable; urgency=low > > + NOT RELEASED > [Fathi Boudra] > - * New upstream release NOT RELEASED (Closes: #337550, #382317) > + * New upstream release (Closes: #319409, #337550, #359932, #382317) > + * Install latex.xml and bibtex.xml provided by kile package instead of > + kdelibs-data (Closes: #358863) > > -- Fathi Boudra <fboudra@free.fr> Sat, 19 Aug 2006 15:45:38 +0200 > > > Modified: kde-extras/kile/trunk/debian/kile.install > ==================================================================> --- kde-extras/kile/trunk/debian/kile.install 2006-08-25 09:23:25 UTC (rev 4396) > +++ kde-extras/kile/trunk/debian/kile.install 2006-08-25 09:23:38 UTC (rev 4397) > @@ -2,6 +2,8 @@ > usr/share/applications/kde/kile.desktop > usr/share/apps/kconf_update > usr/share/apps/kile > +usr/share/apps/katepart/syntax/bibtex.xml > +usr/share/apps/katepart/syntax/latex.xml > usr/share/config.kcfg/kile.kcfg > usr/share/doc/kde/HTML/en/kile > usr/share/icons > > > -- > http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-commits > >-- To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it. -- reddy@lion.austin.ibm.com
Le vendredi 25 ao?t 2006 12:05, Achim Bohnet a ?crit :> Everything IMHO of course: I don''t like this change (and some kate > but not kile latex user here will agree).sure, and the opposite too.> The highlighing should be available as soon as when kate(part) is installed. > Not only when kile is installed.> I would suggest to update kdelibs-data in case the kile one are more > recent. *Or we somehow organize a *data-extra pkg. AFAIR these > problems occured already several times with mimetype defs too :( )kile one are always more recent.> Would be best kile upstream adds their higlighing in KDE branch > so branch pulls would fix it. Or one of the team does the sync ;)please see: http://sourceforge.net/mailarchive/forum.php?thread_id=9874362&forum_id=34317 and multiple private request from upstream developers to do this. Fathi
Le vendredi 25 ao?t 2006 12:05, Achim Bohnet a ?crit :> On Friday 25 August 2006 11:23, Fathi Boudra wrote: > > Author: fboudra-guest > > Date: 2006-08-25 09:23:38 +0000 (Fri, 25 Aug 2006) > > New Revision: 4397 > > > > Modified: > > kde-extras/kile/trunk/debian/changelog > > kde-extras/kile/trunk/debian/kile.install > > Log: > > Move bibtex.xml and latex.xml from kdelibs-data to kile package > > Everything IMHO of course: I don''t like this change (and some kate > but not kile latex user here will agree). The highlighing > should be available as soon as when kate(part) is installed. Not only > when kile is installed. > > I would suggest to update kdelibs-data in case the kile one are more > recent. *Or we somehow organize a *data-extra pkg. AFAIR these > problems occured already several times with mimetype defs too :( ) > > Would be best kile upstream adds their higlighing in KDE branch > so branch pulls would fix it. Or one of the team does the sync ;)i forget to mention some times ago this thread: http://lists.alioth.debian.org/pipermail/pkg-kde-talk/2006-June/000499.html where nobodies replied... All peoples involved can now take part to the thread as i cc the mail to upstream, and give their point of view. Fathi
irc discussions:
14:52 < allee> fabo: yeah, the problem sucks. we''ve been there
several times
already.
14:53 < allee> fabo: from a distro point of view the optimal solution is
to
update the xml files kdelibs-data. We don''t have to care about
kompatibility
with KDE 3.2
14:55 < fabo> allee: kile devs must update (sync) their files in the 2
repo
(kile + kde)
14:55 < allee> a compromise from the easy of maintaince may be to use
alternatives and prio related to version
14:55 < fabo> or we need to create a meta like with these file
14:56 < fabo> i prefer an upstream resolution if possible
14:57 < allee> fabo: me too. So sync kile, kde branch(es) is the leasst
thing
they can do for use ;)
14:57 < allee> fabo: but upstream can''t sole the problem
completely for us
because they can''t know when/if a branch pull is done.
15:00 < fabo> allee: they say that kile ones are the most up-to-date,
maybe a
script can "automagically" update kde svn ? independent (?) from our
branch
pull
15:04 < allee> fabo: would it be too painful to add a grep test to
compare
installed kdelibs-data *.xml version with the one in kile and that FBTFS if
kile has a more recent one? (need build-dep on
kdelibs-data)
15:06 < allee> mhmm, or an optional test (like pkg specific lintian check)
+
alternative for the two files.
15:06 < fabo> allee: yes, this is a possile solution
15:07 < allee> fabo: this may we^you ;) get an reminder to update .xml
files
in kdelibs-data and when kile is installed the kile always(?) more recent
verson is used
15:12 < fabo> allee: hmm maybe we can just add a test in the branch pull
to
keep these files up-to-date ?
15:13 < fabo> allee: to resume-> we keep these file in kdelibs-data and
in the
branch pull we extract the most up-to-date files
15:16 < allee> fabo: mhhm, I not sure about readability of branchpull
scripts
if we have to add more and more such checks over time.
15:18 < fabo> allee: just an extra check for this particular case, or an
other
script can do it without touching branch pull
15:18 < allee> fabo: so decitated test in kile (or other apps seem more
appealing to me). Assumed that the individual pkg maintainer know more about
the pkg specific test
15:19 < fabo> allee: anyway we''ve got some possible solution
15:20 < fabo> allee: i''ll post the discussion and wait for
feedbacks from
upstream and maybe others Thucydides ? MadCoder ? ... ?
15:20 < MadCoder> fabo: honnestly, I don''t care much about the
problem
15:20 < MadCoder> I don''t use kate
15:20 < MadCoder> ;P
15:20 < MadCoder> I feel it''s better to have the one most up to
date
15:21 < MadCoder> but I also feel wrong not to ship one if kile is not
here
15:21 * fabo kicks MadCoder
15:21 < fabo> so the goal is clear, just how we''ll do it :)
15:21 < allee> fabo: but: when this test triggers on out of date data in
kdelibs-data. It the maintainer (or a sciript), create a patch for
kdelibs-data, check in upstream version ind kde_branch is uptodate ->
otherwise remind/pester upstream to do it
15:23 < MadCoder> fabo: alternatives ?
15:24 < allee> MadCoder: only alternatives means that without kile your
latex/bibtex highlightning in kate(part) may be out of date
15:26 < MadCoder> so ?
15:26 < MadCoder> that''s a fair trade between features and amount
of work to
throw in
15:26 < MadCoder> else the good way is to do the sync manually into
kdelibs-data for those who have commit rights
15:26 < MadCoder> but it needs work, and may hurt prides
15:27 < allee> :)
15:29 < allee> fabo: I''ll try to scriptify the version comparison
15:29 < fabo> allee: ok
Thomas Braun
2006-Aug-26 14:03 UTC
Keeping kile''s syntax files [was: Re: rev 4397 - kde-extras/kile/trunk/debian]
Hello, in principle it should be no problem for us to keep the kate files up to date but in practise ... I would suggest one of the following solutions: 1) Using debians divert mechanism, it sounds like what we need http://www.debian.org/doc/debian-policy/ap-pkg-diversions.html. Users without kile have kate''s syntax files and kile users have kile''s syntax files. Or using alternatives!? 2) Making symlinks from kate''s syntax files to kile''s syntax files. SVN starting from 1.1 supports this, but I don''t know if it is wanted that one makes links from main KDE to extragear or vice versa. Thanks for your help maintainers Thomas Braun
Fathi Boudra
2006-Aug-26 15:20 UTC
Keeping kile''s syntax files [was: Re: rev 4397 - kde-extras/kile/trunk/debian]
hi, atm, to resolve the problem, we''ll keep syntax file in kdelibs-data, and we are writing a shell script to keep up-to-date syntax file. see current idea: http://paste.debian.net/11620 then we can do the sync, or ping you to do it ... cheers, Fathi