Hi, El Jueves, 7 de noviembre de 2013 14:42:00 Ritesh Raj Sarraf escribió: > On Thursday 07 November 2013 01:28 AM, David Suárez wrote: > > Hi, > > > > El Miércoles, 6 de noviembre de 2013 12:00:39 Ritesh Raj Sarraf escribió: > >> Hello David, > >> > >> Please provide the changes. I'll look into it. Preferably in some git > >> location. > > > > There goes: https://github.com/deiv/bespin-pkg > > > > One thing to note is, that I switch to use tarballs for upstream import. > > So > > now, the repository layout is completely based on git-buildpackage tools > > layout (master, upstream and pristine-tar branches are the ones in use). > > Does it have any benefits? AFAIK, Thomas still does not do a release.
Matter of taste. I prefer to stay with the debian packaging history only, instead of having all the upstream history merged. About the tarball, Im using the one generated from the HEAD. > In debian/rules: > > override_dh_auto_clean: override_dh_auto_configure > cd build && make clean > $(RM) -R build $(UNCLEANED_FILES) > > override_dh_auto_configure: > test -d build || mkdir build > cd build && ln -sf ../debian && cmake > -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` -DCMAKE_BUILD_TYPE=Release .. > > > > This ends up bringing in all the -dev packages outside my pbuilder > setup. I do not want to have the -dev packages installed on my regular > box. Can you work around this? A simpler clean target, that doesn't have > package dependencies, would be better. Fixed. Thanks, David _______________________________________________ pkg-kde-extras mailing list email@example.com http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras