Re: Autoconf build targets
Robert Millan wrote:
They will have to use the package. This is basically not going to be
optional for a while. Sorry, but Debianized and reliable are my
priorities for the freebsd source package right now. Flexibility
features are going to have to wait.
On Sun, May 19, 2002 at 06:51:34PM -0400, Nathan Hawkins wrote:
Matthew Garrett wrote:
I've already done this in freebsd-kernel package. It's patched
automatically, so it should be included when I have the source package
setup to so that users can build their own kernels.
1) Modify the kernel build so uname -v includes "Debian" - this is a
pretty trivial change. It does present problems if people build kernels on
their own - one option would be to make sure that the kernel build system
ensures that this is set.
This means that people building packages will have to be running a
patched version of the kernel?
At some point when I have time to spend on it, (no really bad bugs to
work on) I will try to make tools to make it possible to build a kernel
with a user-supplied configuration, and generate a package from it.
Something like make-kpkg, although the situation is significantly different.
In the case of FreeBSD, the main reason why user-space packages check
for that is to see if they are building ELF or a.out, or how to do
shared libraries. This is for old versions of FreeBSD that I see no
reason to support.
It looks weird to me, also some packages checking for kernel version
might have trouble.
Also uname -r provides the release version, which is what packages will
Because one of the "resources" we're looking for is Debian. Specific
example: libtool on regular FreeBSD uses a completely different scheme
for soname versions. It uses libfoo.so.1, never libfoo.so.1.0.0, symlink
libfoo.so.1 -> libfoo.so.1.0.0 and soname libfoo.so.1, as Linux and most
other systems do. On Debian, this needs to be done as Linux does it,
because doing the FreeBSD style breaks far too many package build
scripts. It breaks virtually every package in fact. Definitely every
package using dh_movefiles.
Why don't you just check for the particular resource you need in every
particular case (preferably using autoconf)?
So what I want libtool to look at is: is this system FreeBSD or Debian
GNU/FreeBSD, and do something different depending on the answer.
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com