Compilation Question

> DNS has already written helpers to free KDE Parabola-style, which
> is a
> good thing, because I really don't know what I am doing as far as
> helpers and lack that kind of skill.
>
> Thanks so much for the tip. I'll poke my nose in the Debian docs and
> see what I can learn about debian/control.

Digging around to find the answer for myself I see that one
increments the revision of a package with a dch -i .

However, I also realised I answered your question, not your problem.
You could just as easily stop kdelibs being updated by pressing = for
hold against the package name in the aptitude ui.

> I still want to know how to do this though, because the end game,
> if I
> can get it right, would be to recompile Trisquel on the quad-core,
> native to atom processors to install on the netbook. Playing with
> kdelibs is just a way to (hopefully) get the method down.

Oh, a distinctly non-trivial exercise. Yes, then maint-guide and the
reading it recommends is the best answer I know. But, you might try
PMing jxself (or maybe he'll chip in here) to ask him if he knows a
better way to learn .deb packaging - I just tinker, he maintains that
linux-libre repo. You might also try Francesco Mateotti on the
trisquel-devel mailing list (he last posted in April) to see what he
has learnt about the Trisquel makeiso process in the git when you get
to the point of considering an install disk.

Leny

OK, I don't actually know the answer because the package helpers handle all this for you. I just know where you're supposed to be able to find it (as I said I tinker).

My understanding of maint-guide is that << means strictly-less-than. So you are telling it that it is incompatible with and replaces anything less than 4.8.5. Which would seem to make little difference as the Trisquel repo is above that level already.

However, in parallel I have been experimenting on hello-debhelper which is the recommended learning package. I downloaded it with a

apt-get source hello-debhelper
cd hello-debhelper/tab/

and modded it to personalize the traditional greeting to "hello Leny\n"
Then did a

dpkg-source --commit

Leaving the release in debian/changelog unchanged when my editor came up (you need to read package debian-policy to know what to put there). According to maint-guide this is the file the actual package version / release etc is stored in. Then a

dpkg-buildpackage
cd ..
sudo dpkg -i hello-debhelperTAB

This installed the package, but

sudo apt-get update
sudo apt-get upgrade

wanted to replace it.

I then did

cd helloTAB
dch -i

Which gave me my editor with the release part of the package name which is in parens having a .1 appended to the end. I filled the changelog in as best I was able and built the package again with

dpkg-buildpackage

and installed the .deb from one directory above as before. This time I was not offered an update by apt-get update; apt-get upgrade. The problem is I don't know for sure if I would be offered an upgrade should the package be updated in the Trisquel repos.

But in reading the Debian Linux Kernel Handbook ( http://kernel-handbook.alioth.debian.org/ch-common-tasks.html ) this week I noticed they said that a ~ in the suffix indicates a pre-release version. So you might experiment with a suffix of ~6.0trisquel1 after any ubuntu string in debian/changelog which would be the pre-release suffix for the first Trisquelization. Then watch for DNS's updates (which aren't in any of the git repos I know of yet) arriving on another computer (or better setup a small virtual machine to test). Unless you've got some desperate passion to build a small repo at home and experiment that is. I've no idea about that.

I'd be interested to hear what you've done if you do get it to work.