Re: Modifying a source package for a custom install
On Fri, Jul 19, 2002 at 11:06:42AM -0400, rich wrote:
> I've got a number of questions. Some of them generic to customizing
> source packages, some of them specific to apache-ssl.
>
> Is there a standard/documented way of customizing source packages?
What you've done is pretty much fine. You probably want to add an entry
to the top of debian/changelog so that the version number of the .deb
that's produced is different from any in the archive; exactly what you
pick depends on how you want upgrading to behave.
> I don't really need to produce a .deb file. Is anything lost if I cd to
> 'build-tree/apache' and do 'make install' after the 'build' step?
If you do that, you probably want to customize the build process so that
it installs into /usr/local (or /opt if you prefer that). Those
directories won't be scribbled over by Debian packages, while if you
install into /usr without using a .deb a later package installation may
overwrite your changes.
> building apache-common seems redundant after building apache-ssl for a
> custom install. Must I do both?
You could install the appropriate version from the Debian archive, as
long as you don't want to customize its directory layout. Alternatively
you can tweak the expected version of apache-common in the debian/
directory to match what you're building against; I think it might be
hard-coded at the moment.
> I can think of a few packages I'd like to make more minor changes to
> (compiler flags & such) how should I do that in the "proper Debian way"?
As I say, you're pretty much there. There has been some initial
development of a tool called apt-src to let you do this and track
upgrades at the same time, but I'm not sure if it's ready for general
consumption yet.
Cheers,
--
Colin Watson [cjwatson@flatline.org.uk]
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: