From: Enrico Scholz (enrico.scholz_at_informatik.tu-chemnitz.de)
Date: Mon 27 Dec 2004 - 22:02:15 GMT
kk_at_verfaction.de (Kilian Krause) writes:
>> > | * /etc/vserver/util-vserver-vars
>> Please do not install 'util-vserver-vars' into /etc.
> Yet the option to allow a relocation of the default vserver rootdir
> would be highly appreciated. (and IMHO broken if not availble at all)
The default vserver rootdir is determined by the '--with-vrootdir'
configure option. But this is used at very few places only.
Root-directory of existing vservers is /etc/vservers/.../vdir and the
location for newly created vservers is based on
>> > | * Both /usr/include/ and /usr/lib/pkgconfig/ are installed by
>> > | default. What is include/vserver.h installed for?!
>> Support for 3rd party language bindings were the main idea behind an
>> libvserver library. Dunno, if there is much interest in such ones but I
>> do not see reasons not to ship the -devel files.
> Has so far only _one_ app been coded outside the util-vserver domain?
Yes, vserver-djinni () ;)
>> > | * The distclean target does also remove util-vserver.spec which is
>> > | shipped in the release tarball.
>> Where is the problem? The corresponding clean-rule is autogenerated
>> by autoconf and the file can be recreated by './configure' resp.
> The point is you don't delete files you ship in the release tarball.
> Thus if the spec is included in the official tarball the clean shouldn't
> remove it.
Sorry, I do not know how to change this. This file is added by automake
to the $(CONFIG_CLEAN_FILES). After automake.info, I am doing the right
| * If `configure' built it, then `distclean' should delete it.
Vserver mailing list