You are not logged in.
(Mods - if this is the wrong place for this, feel free to move it).
I've been trying to put together a PKGBUILD for ipsec-tools, and I've finally got it to compile (See this thread for details). When I try to install it, however, I get a conflict warning, saying that /usr/man/man8/setkey.8.gz already exists. Pacman tells me that the file comes from the iputils package, but I don't understand why it's there - iputils does not include setkey itself.
Can anyone clarify this?
Offline
good question - is that manpage included in the main source for iputils?
what I've done in cases like that is compare the man pages... if they match pretty well, just "rm" the new one in the PKGBUILD after a make install...
Offline
good question - is that manpage included in the main source for iputils?
It turns out that it does, but there's more to it than that. It seems the iputils guys have decided to incorporate the entire ipsec-tools source into iputils:
[021109]
* added racoon. It is too hairy and will be split in the next snapshots. <==
However, at current stage iputils is the most convenient place to compile
it, because iputils privides necessary infrastructure to cure madness
of glibc and import uptodate API defintiions.[021108]
* Noah L. Meyerhans <frodo@morgul.net> Wow. == instead = in traceroute6.
* Port of libipsec and setkey from KAME. ME. <==
* Add option -P ipsec_policy to ping. ME.
* Disassemble KAME setkey(8 ) manpage and make necessary modifications
to reflect our differences.
racoon, setkey, and libipsec make up ipsec-tools. The Arch iputils package does not install these binaries. However, it does install all the man pages, hence the inclusion of man setkey without setkey itself.
Offline
Arch uses a patch, which among others, disables building certain things:
-ifeq ($(KERNEL_INCLUDE)/linux/pfkeyv2.h,$(wildcard $(KERNEL_INCLUDE)/linux/pfkeyv2.h))
- SUBDIRS=libipsec setkey
- LDLIBS+=-Llibipsec -lipsec
- IPSECDEF=-DDO_IPSEC -Ilibipsec
-endif
-
Time for you to post a new bug in the bugtracker asking why this is, and if there is no good reason to please enable the build of the other tools, and if not, to remove the stale manpages?
Offline
Done - and thanks for deciphering that patch, i3839. I hadn't a clue what it meant...
Offline
Patches are very simple, really: Lines with a '-' in front of them mean that that line is removed, and lines with '+' in front of them are added lines. The rest are context lines around the places where -/+ happen. At least for unified diffs (patches made with diff -u), there are other formats, but this one is most common.
Offline