| 1 |
Hi, |
| 2 |
|
| 3 |
> Sorry for my very long silence. I had to deal with some GSoC problems, |
| 4 |
> especially with the fact that my mentor gave up. I've got a new |
| 5 |
> mentor now, which is Luca Bartodo. Thanks to him for helping me! |
| 6 |
> |
| 7 |
> It's been hard to remotivate myself working on the project: I've to |
| 8 |
> admit I've lost 1 week, stuck between waiting Davide's come back, |
| 9 |
> asking myself a lot of questions I had to ask to Davide, and, tons of |
| 10 |
> problems related to my project. |
| 11 |
|
| 12 |
I didn't know you were left alone; if you need some help you can |
| 13 |
contact me too; unfortunately I'm way too busy these days to be able to |
| 14 |
be a full mentor but I'm interested in seeing a g/netbsd port so I can |
| 15 |
give a high priority in helping you towards that goal :) |
| 16 |
|
| 17 |
|
| 18 |
I've a couple of remarks wrt |
| 19 |
http://projects.boulz.org/trac/gentoo-nbsd/attachment/wiki/WikiStart/netbsd-gentoo-ebuilds.txt |
| 20 |
|
| 21 |
netbsd-bin |
| 22 |
| sh -> app-shells/bash = OK |
| 23 |
|
| 24 |
This doesn't sound optimal; I'd rather keep netbsd sh which is probably |
| 25 |
a POSIX compliant sh and leave bash as /bin/bash; while in practice this |
| 26 |
is not always the case, all gentoo packages should be fine with /bin/sh |
| 27 |
not being bash. Esp. openrc works very well with a more |
| 28 |
lightweight /bin/sh than bash and thus makes booting faster. |
| 29 |
|
| 30 |
netbsd-sbin |
| 31 |
| rcorder -> nothing = OK |
| 32 |
|
| 33 |
rcorder is the thing that does a topological sort on init script |
| 34 |
dependencies, right? In that case, with openrc it's very unlikely to be |
| 35 |
needed but IMHO it would be nice to have it available (an useflag?). |
| 36 |
|
| 37 |
netbsd-ubin |
| 38 |
14 | m4 -> sys-devel/m4 = OK |
| 39 |
15 | patch -> sys-devel/patch = OK |
| 40 |
22 | sed -> sys-apps/sed = OK |
| 41 |
|
| 42 |
Be careful there: all of them prepend the binaries names with a g when |
| 43 |
userland isn't gnu. On FreeBSD, with portage we use the GNU versions |
| 44 |
(see profiles/default/bsd/fbsd which aliases them) but BSD versions have |
| 45 |
been preferred as, respectively, m4, patch and sed. This raises the |
| 46 |
question: what userland do you want to have? IMHO it is better to have |
| 47 |
a full BSD userland while stuff that require GNU tools can use the g |
| 48 |
prefixed tools; with that idea you can see portage as a pkgsrc |
| 49 |
replacement (or ports replacement in case of fbsd) instead of a |
| 50 |
different system with a netbsd kernel & libc but with the rest of it |
| 51 |
being GNU. |
| 52 |
|
| 53 |
17 | yacc -> sys-devel/bison = OK |
| 54 |
|
| 55 |
Here too: On FreeBSD we use yacc from freebsd-ubin. bison ebuild should |
| 56 |
be fine with that and won't install the yacc symlink. |
| 57 |
|
| 58 |
24 | uuidgen -> sys-apps/e2fsprogs = FAIL |
| 59 |
|
| 60 |
Keep it there and don't worry about the e2fsprogs version. The e2fsprogs |
| 61 |
version uses libuuid which shouldn't be needed on BSD. I'm not sure |
| 62 |
about netbsd, but freebsd has uuid functions in the libc; they come |
| 63 |
with a different interface but do the same thing. See eg |
| 64 |
https://bugs.gentoo.org/show_bug.cgi?id=270003 |
| 65 |
Otherwise you'll need libuuid from util-linux, and good luck getting |
| 66 |
something working on BSD out of it. |
| 67 |
|
| 68 |
netbsd-usbin |
| 69 |
42 | lp,lpc,lpd,lpq,lpr,lprm,lptest,pac->net-print/cups=FAIL |
| 70 |
43 | postfix (MKPOSTFIX) -> mail-mta/postfix = FAIL |
| 71 |
44 | wpa_* -> net-wireless/wpa_supplicant = FAIL |
| 72 |
|
| 73 |
We should probably address these. What's the failure there? |
| 74 |
|
| 75 |
|
| 76 |
netbsd-libs |
| 77 |
49 | libss -> sys-libs/ss = OK |
| 78 |
|
| 79 |
sys-libs/ss shouldn't be used, take the one from e2fsprogs-libs. |
| 80 |
|
| 81 |
54 | libpcap -> net-libs/libpcap = FAIL |
| 82 |
|
| 83 |
What's the problem here? |
| 84 |
|
| 85 |
55 | libcom_err -> sys-libs/e2fsprogs-libs with |
| 86 |
"--disable-tls" ./configure flag = OK |
| 87 |
|
| 88 |
What's the problem with tls? |
| 89 |
|
| 90 |
|
| 91 |
About the ebuilds in the overlay: |
| 92 |
|
| 93 |
netbsd-kernel -> usually we name kernel as -sources: gentoo-sources, |
| 94 |
freebsd-sources, etc. |
| 95 |
|
| 96 |
netbsd-binutils, netbsd-gcc: what's the point of these wrt |
| 97 |
sys-devel/{binutils,gcc} ? |
| 98 |
|
| 99 |
wrt the way you disable bundled libs (eg in netbsd-libs): can't this be |
| 100 |
done on a more generic way than patching, like the way freebsd.eclass |
| 101 |
does with REMOVE_SUBDIRS ? Doesn't dummy-mk from bsdmk.eclass work on |
| 102 |
netbsd makefiles? |
| 103 |
|
| 104 |
> Another problem I face is Kerberos libraries compilation. It fails to |
| 105 |
> compile with this error: |
| 106 |
> http://pastebin.org/8892 |
| 107 |
|
| 108 |
Sounds like openssl related; what provides /usr/include/openssl/evp.h ? |
| 109 |
|
| 110 |
> I also have to change two ./configure args which are "--without-et" |
| 111 |
> and "--without-ss" to pass configure script. According to ./configure |
| 112 |
> help: --with-system-et use system compile_et and -lcom_err [default: |
| 113 |
> build and install a local version] |
| 114 |
> --with-system-ss use system -lss and mk_cmds [private version] |
| 115 |
|
| 116 |
Why do you need this? e2fsprogs-libs should provide libcomm_err and |
| 117 |
libss and we should seriously avoid using bundled libs in packages. |
| 118 |
|
| 119 |
> I'd like to know how did Gentoo/FreeBSD managed with Kerberos |
| 120 |
> librairies ? Even by reading ebuilds, I can't really understand. Some |
| 121 |
> help would be appreciated. |
| 122 |
|
| 123 |
That I'm afraid I don't know :/ |
| 124 |
|
| 125 |
> I think we are near the end :) |
| 126 |
|
| 127 |
Great! |
| 128 |
|
| 129 |
|
| 130 |
Alexis. |
Archives