Hi, I'm working on debs for keg modules libexif, libkipi, kipi-plugins and digikam (as test app) to ease preparation by a DD or ITP them later myself when they will be released (maybe end of august??)
Untils the upstream release: I find it quite inconvinient to create a tar ball and then follow the std procedure again and again (I've to copy every change back to kde cvs. Has anyone some tips, URLs, how to best 'prepare' a deb pkg inside kdeextragear cvs? What I would like to do is to cvs up make -f Makefile.cvs cd <module> while ! happy; do whats-necessary; debuild; dpkg -i ../xxx; test; test; test done Appended are my current work arounds. I hope someone found something better, to deal with the problem. Any hint & tip appreciated! After the upstream release: Has anyone a script that makes it simpler to incorporate changes between the .orig.tar.gz and a (stable) branch into debian/patches/*? Ditto vice versa possible changes in src tree back into kde cvs tree? Achim P.S. here my kde cvs workaround For the kdebluetooth rules I use hacks like ifeq "$(wildcard ./admin)" "" # okay uppacked tar ball else # in keg*/<module> fi and for libkexif/kipi kipi-plugins,digican (with cdbs) stuff like: cat <keg-x>/<module>/configure #!/bin/bash cd .. && ./configure "$@" works for all but kipi-plugins where I also have to add ln -s . obj-i386-linux still to investigate why cdbs created where a obj-i386-linux build dir and not in the other cases. Achim -- -> . 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. -- [EMAIL PROTECTED]