|
There is a question or two in the last three paragraphs--the rest I guess you could say is background.
Background:
I've now followed Alenjandro's advice, and compiled the application myself and installed it to a directory.
The version that I compiled was actually 4.14.n. (I forget what it was marked--I think it was the latest version as of yesterday, and I can't easily check the version in kate--see below for an explanation.)
It works fine for me, but I'd mention these shortcomings:
* I did not install kdelibs5-dev version 4.14.n on my system--during the compile it complained about that, but I forced it to compile anyway, and most things seem to work--in particular, the bug fix that I needed (which is incorporated in version 4.11.n) is present and works! * Also during the compile it warned me that the kactivities file was not present--I installed a kactivities file from wheezy (i.e., kde 4.8.4) (I think I got it by installing libkactivities, iirc), but even then it wasn't recognized. So, I suspect the version of kate that I compiled will not work as a kactivity (but, at this point I don't care, I don't quite know what a kactivity is and don't use it / them). * Because I compiled against version 4.8.4, kate still reports its version as kate 3.8.4 on kde 4.8.4, but I know for sure it is version 4.14.n for a few reasons, among them that the bugfix that I needed, which is not present in 4.8.4) is there in the compiled version of kate.
Question(s):
I'm guessing that this could be of value to someone else, so I have thoughts of making it available somehow--I'm guessing (but don't know for sure) that all I'd have to "package up" is the binary, and maybe the other contents of the directory the binary is in.
Does this now constitute a "backport", or a significant beginning to a backport, and if so, what should I do to make it a backport.
I have read the Debian guidelines for backports, and I'd have to say that I don't think I have the expertise (or the time) to continually update this as new changes are made to kate 4.14
Randy Kramer
On Friday, October 17, 2014 02:50:09 AM Alejandro Exojo wrote: > El Friday 17 October 2014, Randy Kramer escribió: > > I've searched the list of backports to see if anyone had done this, and, > > unless I missed something, no one has. > > > > I wonder if anyone is working on it? > > > > I've done some googling, and am thinking about trying to backport kate > > (at a version of 4.11.n or greater) to wheezy. I've found the > > SimpleBackportCreation page, and if I try it, I will try to follow those > > instructions. > > > > But, I'm wondering, as a newbie to all this, is there much chance of me > > being successful? Will I run into a problem with hundreds of > > dependencies? Will I mess up kde 4.8.4 on my wheezy system? > > > > Opinions and advice solicited. > > Lisandro alreagy gave you good advice on the challenge that it can be. I > see that you are already having trouble. > > One way that might be simpler (not that much in this case maybe), but that > always tends to be cleaner, is to compile the application yourself and > install it to a directory. That leaves your system untouched (you can do > this without root permissions to be fully sure), and you can start the > application setting some environment variables. > > For this case is not that easy because kate 4.11 requires kdelibs 4.11 as > well, so you need to compile kdelibs to a directory, and then tell kate to > use kdelibs for that directory, but is doable. > > I don't recommend it though, if you at least don't fully understand how the > PATH variable works and are somewhat familiar compiling applications.
|