Re: customizing debian apache

[Patrick Hsieh]

Hello,
I think your method is very wise. But after I download the apache source
by "apt-get source apache", how can I rename the package so that I can
build my cusmomized .deb packages?

Usually, I'll dpkg-source -x .dsc, then
cd 
dpkg-buildpackages -uc -us -rfakeroot

This will build .deb packages, right?
But what files or directories should I rename?





--
My suggestion:

apt-get source apache

rename the package, to something like apache-cmore
edit the debian/control to have it "Provide" apache, and "Conflicts"
with apache.

Yes, this is still harder to maintain with new versions, but it is still
fairly tidy. An alternative would be patching suexec to accept a run-time
path (from what I gather, this is non-trivial)

--
Patrick Hsieh--<[EMAIL PROTECTED]>

Re: customizing debian apache

[Patrick Hsieh]

Hello,
I think your method is very wise. But after I download the apache source
by "apt-get source apache", how can I rename the package so that I can
build my cusmomized .deb packages?

Usually, I'll dpkg-source -x .dsc, then
cd 
dpkg-buildpackages -uc -us -rfakeroot

This will build .deb packages, right?
But what files or directories should I rename?





--
My suggestion:

apt-get source apache

rename the package, to something like apache-cmore
edit the debian/control to have it "Provide" apache, and "Conflicts"
with apache.

Yes, this is still harder to maintain with new versions, but it is still
fairly tidy. An alternative would be patching suexec to accept a run-time
path (from what I gather, this is non-trivial)

--
Patrick Hsieh--<[EMAIL PROTECTED]>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: customizing debian apache

[Jeremy C. Reed]

On Fri, 9 Nov 2001, Jason Lim wrote:

> Anyway, as Jeremy said (and much to our fustration) the suexec source
> included is missing critical files required for compilation, so we grab
> the apache source code and just build suexec (think i've mentioned this
> before... anyway).

I guess I didn't explain it very well -- I have used sed several times on
several different systems to patch the actual /usr/lib/apache/suexec
binary executable. (So no need to rebuild from source.)

> > $ cat -v sed.expression
> > s/\/home\/httpd\/html/\/[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL 
> > PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@^@/

  Jeremy C. Reed
..
 ISP-FAQ.com -- find answers to your questions
 http://www.isp-faq.com/

Re: customizing debian apache

[Jeremy C. Reed]

On Fri, 9 Nov 2001, Jason Lim wrote:

> Anyway, as Jeremy said (and much to our fustration) the suexec source
> included is missing critical files required for compilation, so we grab
> the apache source code and just build suexec (think i've mentioned this
> before... anyway).

I guess I didn't explain it very well -- I have used sed several times on
several different systems to patch the actual /usr/lib/apache/suexec
binary executable. (So no need to rebuild from source.)

> > $ cat -v sed.expression
> > s/\/home\/httpd\/html/\/home^@^@^@^@^@^@^@^@^@^@^@/

  Jeremy C. Reed
..
 ISP-FAQ.com -- find answers to your questions
 http://www.isp-faq.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: customizing debian apache

[Jason Lim]

Apparently the path is hardcoded into suexec for "security reasons", so...

Anyway, as Jeremy said (and much to our fustration) the suexec source
included is missing critical files required for compilation, so we grab
the apache source code and just build suexec (think i've mentioned this
before... anyway).

Sincerely,
Jason Lim

- Original Message -
From: "Jeremy C. Reed" <[EMAIL PROTECTED]>
To: "Matt Hope" <[EMAIL PROTECTED]>
Cc: 
Sent: Friday, November 09, 2001 11:39 AM
Subject: Re: customizing debian apache


> On Thu, 8 Nov 2001, Matt Hope wrote:
>
> > fairly tidy. An alternative would be patching suexec to accept a
run-time
> > path (from what I gather, this is non-trivial)
>
> The apache-common package comes with some suexec source. But I am not
sure
> why -- since it is unusable because it is missing several more headers.
>
> Anyways, I often use sed to patch suexec:
>
> $ cat -v sed.expression
> s/\/home\/httpd\/html/\/[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL 
> PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@^@/
>
>   Jeremy C. Reed
> ..
>  ISP-FAQ.com -- find answers to your questions
>  http://www.isp-faq.com/
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
> http://www.zentek-international.com
>

Re: customizing debian apache

[Jeremy C. Reed]

On Thu, 8 Nov 2001, Matt Hope wrote:

> fairly tidy. An alternative would be patching suexec to accept a run-time
> path (from what I gather, this is non-trivial)

The apache-common package comes with some suexec source. But I am not sure
why -- since it is unusable because it is missing several more headers.

Anyways, I often use sed to patch suexec:

$ cat -v sed.expression 
s/\/home\/httpd\/html/\/[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL 
PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@^@/

  Jeremy C. Reed
..
 ISP-FAQ.com -- find answers to your questions
 http://www.isp-faq.com/

Re: customizing debian apache

[Jason Lim]

Apparently the path is hardcoded into suexec for "security reasons", so...

Anyway, as Jeremy said (and much to our fustration) the suexec source
included is missing critical files required for compilation, so we grab
the apache source code and just build suexec (think i've mentioned this
before... anyway).

Sincerely,
Jason Lim

- Original Message -
From: "Jeremy C. Reed" <[EMAIL PROTECTED]>
To: "Matt Hope" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, November 09, 2001 11:39 AM
Subject: Re: customizing debian apache


> On Thu, 8 Nov 2001, Matt Hope wrote:
>
> > fairly tidy. An alternative would be patching suexec to accept a
run-time
> > path (from what I gather, this is non-trivial)
>
> The apache-common package comes with some suexec source. But I am not
sure
> why -- since it is unusable because it is missing several more headers.
>
> Anyways, I often use sed to patch suexec:
>
> $ cat -v sed.expression
> s/\/home\/httpd\/html/\/home^@^@^@^@^@^@^@^@^@^@^@/
>
>   Jeremy C. Reed
> ..
>  ISP-FAQ.com -- find answers to your questions
>  http://www.isp-faq.com/
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
> http://www.zentek-international.com
>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: customizing debian apache

[Jeremy C. Reed]

On Thu, 8 Nov 2001, Matt Hope wrote:

> fairly tidy. An alternative would be patching suexec to accept a run-time
> path (from what I gather, this is non-trivial)

The apache-common package comes with some suexec source. But I am not sure
why -- since it is unusable because it is missing several more headers.

Anyways, I often use sed to patch suexec:

$ cat -v sed.expression 
s/\/home\/httpd\/html/\/home^@^@^@^@^@^@^@^@^@^@^@/

  Jeremy C. Reed
..
 ISP-FAQ.com -- find answers to your questions
 http://www.isp-faq.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: customizing debian apache

[Matt Hope]

On Wed, 07 Nov 2001, Cameron Moore <[EMAIL PROTECTED]> wrote...

: I am well aware that there are ten different ways to do this the "hard
: way".  I can build apache from the official apache source tarball, but
: I'd like to be able to install a customized deb package that's easy to
: maintain (ie. I don't want to have to go in and hack up the build
: scripts every time I upgrade).

My suggestion:

apt-get source apache

rename the package, to something like apache-cmore
edit the debian/control to have it "Provide" apache, and "Conflicts"
with apache.

Yes, this is still harder to maintain with new versions, but it is still
fairly tidy. An alternative would be patching suexec to accept a run-time
path (from what I gather, this is non-trivial)

\dopey{}

Re: customizing debian apache

[Matt Hope]

On Thu, 08 Nov 2001, Craig Sanders <[EMAIL PROTECTED]> wrote...

: why?
: 
: these are ALL run-time configuration directives.
: 
: edit your apache config and forget about it.

... for all but the previously mentioned su-exec path, which is set at
compile time in the suexec binary.

Re: customizing debian apache

[Craig Sanders]

On Wed, Nov 07, 2001 at 12:49:14PM -0600, Cameron Moore wrote:
> Are you blind?  You quoted what's wrong.  The build scripts assume
> you are installing into /var/www, /usr/lib/cgi-bin, etc as defined in
> the Debian Layout.  I would like to be able to alter the layout in a
> single file, run `./debian/rules build`, and have the build process
> alter the post*, pre*, etc files to adhere to my customizations.

why?

these are ALL run-time configuration directives.

edit your apache config and forget about it.

> I am well aware that there are ten different ways to do this the "hard
> way".  I can build apache from the official apache source tarball, but
> I'd like to be able to install a customized deb package that's easy
> to maintain (ie. I don't want to have to go in and hack up the build
> scripts every time I upgrade).

you don't have to. debian packages don't overwrite configuration files
on upgrade unless you tell them to.

craig

-- 
craig sanders <[EMAIL PROTECTED]>

Fabricati Diem, PVNC.
 -- motto of the Ankh-Morpork City Watch

Re: customizing debian apache

[Cameron Moore]

* [EMAIL PROTECTED] [2001.11.07 00:00]:
> 
> 
> > Look in the the debian dir of the src deb.  The rules, post*, pre*, and
> > apacheconfig files are all hardcoded to assuming the Debian Layout.
> 
> You haven't mentioned what's wrong, or requires customisation...

Are you blind?  You quoted what's wrong.  The build scripts assume you
are installing into /var/www, /usr/lib/cgi-bin, etc as defined in the
Debian Layout.  I would like to be able to alter the layout in a single
file, run `./debian/rules build`, and have the build process alter the
post*, pre*, etc files to adhere to my customizations.

I am well aware that there are ten different ways to do this the "hard
way".  I can build apache from the official apache source tarball, but
I'd like to be able to install a customized deb package that's easy to
maintain (ie. I don't want to have to go in and hack up the build
scripts every time I upgrade).
-- 
Cameron Moore

Re: customizing debian apache

[Jason Lim]

An alternative is the KISS way (keep it simple stupid) way...

Just download the apache source code from www.apache.org, compile suexec
from there, and cp it to the appropriate directory where Debian expects
it.

Works like a charm.

Sincerely,
Jason

- Original Message -
From: "eirik dentz" <[EMAIL PROTECTED]>
To: 
Sent: Thursday, November 08, 2001 12:39 AM
Subject: Re: customizing debian apache


> I actually did this a while back because I wasn't happy with the debian
> default suexec directory either. I don't remember exactly what I did but
> I remember that I started by downloading all the packages necessary to
> build .debs and then I grabbed the apache source files, currently that
> would be:
> apache_1.3.22-2.dsc
> apache_1.3.22.orig.tar.gz
> apache_1.3.22-2.diff.gz
>
> And then I grabbed all the packages listed in the .dsc file.  opened up
> the .diff file in a text editor and searched for "suexec" made my
> changes and then followed the instructions about building a .deb here:
>
> <http://www.debian.org/doc/FAQ/ch-pkg_basics.html#s-sourcepkgs>
>
> Once I figured it out it didn't take all that long and I had suexec
> hardwired to a directory of my choice.  Of course the problem with this
> was that upgrading apache was no longer as simple as issuing apt-get
> update.  So after maintaining my own layout for a few upgrades, I
> scrapped it and went with the Debian default because the ease of apt-get
> update is really one of the things that makes Debian stand above all the
> other Linux distros.  Of course I didn't really have any issues with it
> other than the suexec directory.
>
> HTH
>
> eirik
>
>
> On Wednesday, November 7, 2001, at 12:18 AM, Cameron Moore wrote:
>
> > * [EMAIL PROTECTED] [2001.11.06 22:50]:
> >> 
> >>
> >>> Has anyone managed to customize (as in "use your own Layout on") an
> >>> apache build from .deb source?  I can't stand the debian Layout and
> >>> want
> >>> to customize it (or even use an existing layout that comes with
> >>> apache).
> >>> The problem is that all of the build scripts and whatnot assume you
> >>> use
> >>> the Debian layout.
> >>
> >> Define "layout"?
> >
> > See config.layout:
> >  #   Debian GNU policy conforming path layout.
> >  
> >  prefix:/usr
> >  exec_prefix:   $prefix
> >  bindir:$exec_prefix/bin
> >  sbindir:   $prefix/lib+
> >  libexecdir:$exec_prefix/libexec
> >  mandir:$prefix/share/man
> >  sysconfdir:/etc+
> >  datadir:   $prefix/lib
> >  iconsdir:  $prefix/share/apache/icons
> >  htdocsdir: $datadir/htdocs
> >  cgidir:$datadir/cgi-bin
> >  includedir:$prefix/include+
> >  localstatedir: /var
> >  runtimedir:$localstatedir/run
> >  logfiledir:$localstatedir/log+
> >  proxycachedir: $localstatedir/cache+
> >  
> >
> >> If it's just a matter of "where served files are on the filesystem"
> >> you can
> >> do that very easily post-install.
> >
> > Possibly, but that's not what I want to do.  If you want suEXEC, you
> > have to know the paths at compile-time.  It would be *much* easier to
be
> > able to define an alternative layout and have the deb package build
> > properly.
> >
> >> I'm surprised you'd have any issues with the apache packages - they
> >> are one
> >> of the most well put together and administrator-friendly sets of
> >> packages
> >> I've ever seen.
> >>
> >> Please point out specific issues.
> >>
> >> - Jeff
> >
> > Look in the the debian dir of the src deb.  The rules, post*, pre*,
and
> > apacheconfig files are all hardcoded to assuming the Debian Layout.
> > That's all fine and good, but it restricts customization.  I'm not
sure
> > how foobarred everything would get if a package that depends on apache
> > being in a certain spot, either.  Guess I need to contact the
> > maintainer.  :-)
> >
> > I mainly want to know if anyone has done this before.  If not, I'll
dig
> > through it myself and see what happens.  ;-)  Thanks
> > --
> > Cameron Moore
> >
> >
> > --
> > To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> > with a subject of "unsubscribe". Trouble? Contact
> > [EMAIL PROTECTED]
> >
>
> http://www.zentek-international.com
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
>
>

Re: customizing debian apache

[eirik dentz]

I actually did this a while back because I wasn't happy with the debian 
default suexec directory either. I don't remember exactly what I did but 
I remember that I started by downloading all the packages necessary to 
build .debs and then I grabbed the apache source files, currently that 
would be:
apache_1.3.22-2.dsc
apache_1.3.22.orig.tar.gz
apache_1.3.22-2.diff.gz

And then I grabbed all the packages listed in the .dsc file.  opened up 
the .diff file in a text editor and searched for "suexec" made my 
changes and then followed the instructions about building a .deb here:


Once I figured it out it didn't take all that long and I had suexec 
hardwired to a directory of my choice.  Of course the problem with this 
was that upgrading apache was no longer as simple as issuing apt-get 
update.  So after maintaining my own layout for a few upgrades, I 
scrapped it and went with the Debian default because the ease of apt-get 
update is really one of the things that makes Debian stand above all the 
other Linux distros.  Of course I didn't really have any issues with it 
other than the suexec directory.

HTH
eirik
On Wednesday, November 7, 2001, at 12:18 AM, Cameron Moore wrote:
* [EMAIL PROTECTED] [2001.11.06 22:50]:

Has anyone managed to customize (as in "use your own Layout on") an
apache build from .deb source?  I can't stand the debian Layout and 
want
to customize it (or even use an existing layout that comes with 
apache).
The problem is that all of the build scripts and whatnot assume you 
use
the Debian layout.
Define "layout"?
See config.layout:
 #   Debian GNU policy conforming path layout.
 
 prefix:/usr
 exec_prefix:   $prefix
 bindir:$exec_prefix/bin
 sbindir:   $prefix/lib+
 libexecdir:$exec_prefix/libexec
 mandir:$prefix/share/man
 sysconfdir:/etc+
 datadir:   $prefix/lib
 iconsdir:  $prefix/share/apache/icons
 htdocsdir: $datadir/htdocs
 cgidir:$datadir/cgi-bin
 includedir:$prefix/include+
 localstatedir: /var
 runtimedir:$localstatedir/run
 logfiledir:$localstatedir/log+
 proxycachedir: $localstatedir/cache+
 
If it's just a matter of "where served files are on the filesystem" 
you can
do that very easily post-install.
Possibly, but that's not what I want to do.  If you want suEXEC, you
have to know the paths at compile-time.  It would be *much* easier to be
able to define an alternative layout and have the deb package build
properly.
I'm surprised you'd have any issues with the apache packages - they 
are one
of the most well put together and administrator-friendly sets of 
packages
I've ever seen.

Please point out specific issues.
- Jeff
Look in the the debian dir of the src deb.  The rules, post*, pre*, and
apacheconfig files are all hardcoded to assuming the Debian Layout.
That's all fine and good, but it restricts customization.  I'm not sure
how foobarred everything would get if a package that depends on apache
being in a certain spot, either.  Guess I need to contact the
maintainer.  :-)
I mainly want to know if anyone has done this before.  If not, I'll dig
through it myself and see what happens.  ;-)  Thanks
--
Cameron Moore
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact 
[EMAIL PROTECTED]

Re: customizing debian apache

[Jeff Waugh]

> Look in the the debian dir of the src deb.  The rules, post*, pre*, and
> apacheconfig files are all hardcoded to assuming the Debian Layout.

You haven't mentioned what's wrong, or requires customisation...

> That's all fine and good, but it restricts customization.  I'm not sure
> how foobarred everything would get if a package that depends on apache
> being in a certain spot, either.

The package requiring apache to be in a certain place would be foobarred, in
this instance.

Specifics! What is wrong with it?

- Jeff

-- 
   She said she loved my mind, though by most accounts I had already lost   
it. 

Re: customizing debian apache

[Cameron Moore]

* [EMAIL PROTECTED] [2001.11.06 22:50]:
> 
> 
> > Has anyone managed to customize (as in "use your own Layout on") an
> > apache build from .deb source?  I can't stand the debian Layout and want
> > to customize it (or even use an existing layout that comes with apache).
> > The problem is that all of the build scripts and whatnot assume you use
> > the Debian layout.
> 
> Define "layout"?

See config.layout:
 #   Debian GNU policy conforming path layout.
 
 prefix:/usr
 exec_prefix:   $prefix
 bindir:$exec_prefix/bin
 sbindir:   $prefix/lib+
 libexecdir:$exec_prefix/libexec
 mandir:$prefix/share/man
 sysconfdir:/etc+
 datadir:   $prefix/lib
 iconsdir:  $prefix/share/apache/icons
 htdocsdir: $datadir/htdocs
 cgidir:$datadir/cgi-bin
 includedir:$prefix/include+
 localstatedir: /var
 runtimedir:$localstatedir/run
 logfiledir:$localstatedir/log+
 proxycachedir: $localstatedir/cache+
 
 
> If it's just a matter of "where served files are on the filesystem" you can
> do that very easily post-install.

Possibly, but that's not what I want to do.  If you want suEXEC, you
have to know the paths at compile-time.  It would be *much* easier to be
able to define an alternative layout and have the deb package build
properly.

> I'm surprised you'd have any issues with the apache packages - they are one
> of the most well put together and administrator-friendly sets of packages
> I've ever seen.
> 
> Please point out specific issues.
> 
> - Jeff

Look in the the debian dir of the src deb.  The rules, post*, pre*, and
apacheconfig files are all hardcoded to assuming the Debian Layout.
That's all fine and good, but it restricts customization.  I'm not sure
how foobarred everything would get if a package that depends on apache
being in a certain spot, either.  Guess I need to contact the
maintainer.  :-)

I mainly want to know if anyone has done this before.  If not, I'll dig
through it myself and see what happens.  ;-)  Thanks
-- 
Cameron Moore

Re: customizing debian apache

[Jeff Waugh]

> Has anyone managed to customize (as in "use your own Layout on") an
> apache build from .deb source?  I can't stand the debian Layout and want
> to customize it (or even use an existing layout that comes with apache).
> The problem is that all of the build scripts and whatnot assume you use
> the Debian layout.

Define "layout"?

If it's just a matter of "where served files are on the filesystem" you can
do that very easily post-install.

I'm surprised you'd have any issues with the apache packages - they are one
of the most well put together and administrator-friendly sets of packages
I've ever seen.

Please point out specific issues.

- Jeff

-- 
  Cette menace est très sérieuse.   

customizing debian apache

[Cameron Moore]

Has anyone managed to customize (as in "use your own Layout on") an
apache build from .deb source?  I can't stand the debian Layout and want
to customize it (or even use an existing layout that comes with apache).
The problem is that all of the build scripts and whatnot assume you use
the Debian layout.

I'm not familiar enough with the debian build process to start trying to
hack up a "neutral" build scheme yet, so I'm hoping someone has some
insight into how to attack this problem.

BTW, I'm using woody/testing.
-- 
Cameron Moore