Jason Stubbs wrote:
On Wednesday 13 April 2005 22:06, Mike Frysinger wrote:
On Wednesday 13 April 2005 06:44 am, Martin MOKREJŠ wrote:
I'm not sure how to block the ebuild when user is running 2.6 kernel
(uname(1)?), of when the /usr/src/linux points to 2.6 kernel ... or just
to check whether gentoo-sources or vanila-sources of 2.4 version are
installed?
put this into pkg_setup():
[[ ${KV:0:3} == "2.6" ]] && die "Sorry, this package doesnt support 2.6
kernels"
Better to use the kernel groups eclass of the month for this one. The defining
of $KV will likely be removed from portage down the track.
1)
Jason, can you give me an example. ;) I'm making my first ebuild, so that's
why I came here.
2)
I have more questions hidden in the .ebuild file, but I think I shouldn't be
lazy
and paste them here. ;)
src_compile() {
econf --enable-transarc-paths --enable-namei-fileserver
--enable-full-vos-listvol-switch --with-linux-kernel-headers=/usr/src/linux
--enable-bitmap-later --enable-fast-restart --enable-largefile-fileserver
--enable-bos-new-config || die econf
make CC="$(gcc-getCC)" MT_CC="$(gcc-getCC)" || die make
}
The above results in:
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man
--infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
--localstatedir=/var/lib --enable-transarc-paths --enable-namei-fileserver
--enable-full-vos-listvol-switch --with-linux-kernel-headers=/usr/src/linux
--enable-bitmap-later --enable-fast-restart --enable-largefile-fileserver
--enable-bos-new-config
Why is there "--prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man
--infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib"? OK, I
believe that's because of general Gentoo instalation paths. But see the $subj, the point here is to install
openafs into *standard* locations. In real it doesn't matter for the install process performed by the ebuild,
as it installs files in "manual" way and ignores "make install" step. Still, for
completeness I'd like to see this removed from this ebuild behaviour.
3)
The ebuild as I've said install config file into well-known location. I can imagine
having symlinks from "standard Gentoo places" to them.
Currently I have commented that out.
# symlink configfiles in TransArc location to Gentoo's typical place
# dosym /usr/vice/etc/CellServDB /etc/afs/CellServDB
# dosym /usr/vice/etc/ThisCell /etc/afs/ThisCell
# touch /usr/vice/etc/cacheinfo
4)
Could someone explain me CONFIG_PROTECT_MASK?
# Hmm, what about this?
dodir /etc/env.d
# don't know what's this CONFIG_PROTECT_MASK usefull for
echo 'CONFIG_PROTECT_MASK="/etc/afs/C /etc/afs/afsws"' \
>> ${D}/etc/env.d/01${PN}
echo 'PATH=/usr/afs/bin' \
>> ${D}/etc/env.d/01${PN}
echo 'ROOTPATH=/usr/afs/bin' \
>> ${D}/etc/env.d/01${PN}
Thanks for answer. ;)
Martin
--
[email protected] mailing list
