well, know I know - ran make distclean a few moments too soon. btw - I thought that we had also shifted to apr-util-1.5.x on httpd-2.2.x (but I am probably mistaken).
I ask because I got this reminder from buildconf. So, I shall assume my memory is bad, and get the latest offficial apr-util-1.4.x and run buildconf again, but would appreciate a verification. Thanks all! Michael On Mon, Nov 25, 2013 at 10:18 PM, Reindl Harald <[email protected]>wrote: > > Am 25.11.2013 21:49, schrieb Michael Felt: > > I am wanting to leave the additions I have done (which are not known to > any clean option) and compare that with > > a) the latest T&R > > b) the latest trunk > > > > Is there a "clean" that goes farther than make distclean (i.e., to even > undo whatever buildconf is going to do) > > i would suggest building RPM/DEB packages because they remove orphanes > files and so on > for RPM a modified SPEC from > http://koji.fedoraproject.org/koji/packageinfo?packageID=13558 > and "rpmbuild" should be fine, Debian - not my world > > in case of RPM-SPEC i love they easy way to carry local patches without > touch the tarball and with "rpmbuild -bs httpd.spec" you get a complete > source-rpm containing tarball, spec-file and all patches > > [builduser@buildserver:~]$ cat /rpmbuild/SPECS/httpd.spec | grep patch > Patch1: %{name}-2.4.1-apctl.patch > Patch2: %{name}-2.4.1-deplibs.patch > Patch3: %{name}-2.4.3-layout.patch > Patch4: %{name}-2.4.4-export.patch > Patch5: %{name}-2.4-no-server-header.patch > Patch6: %{name}-2.4-anonymize-header-order.patch > Patch7: %{name}-2.4-anonymize-header-order-core.patch > %patch1 -p1 > %patch2 -p1 > %patch3 -p1 > %patch4 -p1 > %patch5 -p1 > %patch6 -p1 > %patch7 -p1 > # patch in the vendor string > - reduce patches to go with upstream > - removed obsolete patches > - patch out "Server" header from sources > - rebuild with latest fedora-patches > - remove a lot of patches > >
