Re: Creating Source Packages

[Colin Watson]

Jason Ferguson [EMAIL PROTECTED] wrote:
Heres the problem. They build and install fine. However, on the next 
apt-get dist-upgrade, the packages are overwritten with the standard 
ones!

Edit debian/changelog and add an additional entry to the top,
incrementing the version number by 0.0.1. The devscripts package
contains a utility called debchange (or dch) which will help you get the
format right. Then build and install the new package. When a real new
version comes out, you'll get that, but until then your local packages
will remain installed.

I put export CFLAGS='-O2 -march=i686' into my .bash_profile, but 
the rules build seems to ignore it (hence me editing that script).

Yes, debian/rules routinely sets CFLAGS itself. Packages are supposed to
build the same way regardless of their environment.

(By the way, the easiest way to build a package is 'dpkg-buildpackage
-rfakeroot', or, again from the devscripts package, 'debuild'.)

Cheers,

-- 
Colin Watson [EMAIL PROTECTED]

Creating Source Packages

[Jason Ferguson]

I need help with creating source packages (but with a twist). Heres the 
situation.


I want to create i686 replacement packages for my machine. So, using 
gnomeicu as an example, here's what I did:


apt-get source -d gnomeicu
dpkg-source -x gnomeicu...dsc
cd gnomeicu

Now, the standard way to build a package is to do debian/rules build 
at this point. However, to create the optimized packages, I did the 
following:


cd debian
vi rules
(add -O2 and -march=i686 to the $(MAKE) line)

Then I did the debian/rules build.

Heres the problem. They build and install fine. However, on the next 
apt-get dist-upgrade, the packages are overwritten with the standard 
ones! I put export CFLAGS='-O2 -march=i686' into my .bash_profile, but 
the rules build seems to ignore it (hence me editing that script).


HELP!!!

Jason