Hi,
> Sorry for my very long silence. I had to deal with some GSoC problems,
> especially with the fact that my mentor gave up. I've got a new
> mentor now, which is Luca Bartodo. Thanks to him for helping me!
>
> It's been hard to remotivate myself working on the project: I've to
> admit I've lost 1 week, stuck between waiting Davide's come back,
> asking myself a lot of questions I had to ask to Davide, and, tons of
> problems related to my project.
I didn't know you were left alone; if you need some help you can
contact me too; unfortunately I'm way too busy these days to be able to
be a full mentor but I'm interested in seeing a g/netbsd port so I can
give a high priority in helping you towards that goal :)
I've a couple of remarks wrt
http://projects.boulz.org/trac/gentoo-nbsd/attachment/wiki/WikiStart/netbsd-gentoo-ebuilds.txt
netbsd-bin
| sh -> app-shells/bash = OK
This doesn't sound optimal; I'd rather keep netbsd sh which is probably
a POSIX compliant sh and leave bash as /bin/bash; while in practice this
is not always the case, all gentoo packages should be fine with /bin/sh
not being bash. Esp. openrc works very well with a more
lightweight /bin/sh than bash and thus makes booting faster.
netbsd-sbin
| rcorder -> nothing = OK
rcorder is the thing that does a topological sort on init script
dependencies, right? In that case, with openrc it's very unlikely to be
needed but IMHO it would be nice to have it available (an useflag?).
netbsd-ubin
14 | m4 -> sys-devel/m4 = OK
15 | patch -> sys-devel/patch = OK
22 | sed -> sys-apps/sed = OK
Be careful there: all of them prepend the binaries names with a g when
userland isn't gnu. On FreeBSD, with portage we use the GNU versions
(see profiles/default/bsd/fbsd which aliases them) but BSD versions have
been preferred as, respectively, m4, patch and sed. This raises the
question: what userland do you want to have? IMHO it is better to have
a full BSD userland while stuff that require GNU tools can use the g
prefixed tools; with that idea you can see portage as a pkgsrc
replacement (or ports replacement in case of fbsd) instead of a
different system with a netbsd kernel & libc but with the rest of it
being GNU.
17 | yacc -> sys-devel/bison = OK
Here too: On FreeBSD we use yacc from freebsd-ubin. bison ebuild should
be fine with that and won't install the yacc symlink.
24 | uuidgen -> sys-apps/e2fsprogs = FAIL
Keep it there and don't worry about the e2fsprogs version. The e2fsprogs
version uses libuuid which shouldn't be needed on BSD. I'm not sure
about netbsd, but freebsd has uuid functions in the libc; they come
with a different interface but do the same thing. See eg
https://bugs.gentoo.org/show_bug.cgi?id=270003
Otherwise you'll need libuuid from util-linux, and good luck getting
something working on BSD out of it.
netbsd-usbin
42 | lp,lpc,lpd,lpq,lpr,lprm,lptest,pac->net-print/cups=FAIL
43 | postfix (MKPOSTFIX) -> mail-mta/postfix = FAIL
44 | wpa_* -> net-wireless/wpa_supplicant = FAIL
We should probably address these. What's the failure there?
netbsd-libs
49 | libss -> sys-libs/ss = OK
sys-libs/ss shouldn't be used, take the one from e2fsprogs-libs.
54 | libpcap -> net-libs/libpcap = FAIL
What's the problem here?
55 | libcom_err -> sys-libs/e2fsprogs-libs with
"--disable-tls" ./configure flag = OK
What's the problem with tls?
About the ebuilds in the overlay:
netbsd-kernel -> usually we name kernel as -sources: gentoo-sources,
freebsd-sources, etc.
netbsd-binutils, netbsd-gcc: what's the point of these wrt
sys-devel/{binutils,gcc} ?
wrt the way you disable bundled libs (eg in netbsd-libs): can't this be
done on a more generic way than patching, like the way freebsd.eclass
does with REMOVE_SUBDIRS ? Doesn't dummy-mk from bsdmk.eclass work on
netbsd makefiles?
> Another problem I face is Kerberos libraries compilation. It fails to
> compile with this error:
> http://pastebin.org/8892
Sounds like openssl related; what provides /usr/include/openssl/evp.h ?
> I also have to change two ./configure args which are "--without-et"
> and "--without-ss" to pass configure script. According to ./configure
> help: --with-system-et use system compile_et and -lcom_err [default:
> build and install a local version]
> --with-system-ss use system -lss and mk_cmds [private version]
Why do you need this? e2fsprogs-libs should provide libcomm_err and
libss and we should seriously avoid using bundled libs in packages.
> I'd like to know how did Gentoo/FreeBSD managed with Kerberos
> librairies ? Even by reading ebuilds, I can't really understand. Some
> help would be appreciated.
That I'm afraid I don't know :/
> I think we are near the end :)
Great!
Alexis.
|
