Hi all
I've quietly been working on two concurrent issues. One is outside of
the scope for this list, but it's tied to Nexenta or some project
becoming an official Debian port. I don't have time before Monday, but
if someone would be able to generate a list of GPL software and
copyright
Erast Benson wrote:
On Thu, 2009-03-05 at 20:07 +0100, Mario-Lorenz wrote:
Hi,
I'm working on some of the mail-related packages, and found some issues
that I would like to ask which the better way for a fix would be.
a) fetchmail doesnt build because it can not find krb5-config.
It can
Hi Everyone!
If anyone is going to FOSDEM this year I'd love to arrange some sort of
meet-up for those interested in UNIX/(Open)Solaris development. I'm
working hard to try to get the OSUNIX project in shape, but completely
outside that willing to offer any help I can.
I can offer help
Hi guys..
I'm trying to find the latest nexenta-on source package.. Can you push
that somewhere please.. I'm also curious why it's not available already?
Thanks
./C
___
gnusol-devel mailing list
gnusol-devel@lists.sonic.net
Hi all..
I've been tearing apart onnv-gate for a couple months now and have a
very clear idea of what it would take to build an entirely from source
OpenSolaris technology based distribution. I'll probably post patches
and details of my work at a new development list I've setup. I know
Anil Gulecha wrote:
Hi,
configure on curl fails as follows (from config.log)
..
configure:31776: i386-pc-solaris2.11-gcc -c -g -O2 -I/usr/include
conftest.c 5
configure:31782: $? = 0
configure:31802: result: yes
configure:31818: checking run-time libs availability
configure:31846:
Anil Gulecha wrote:
Yup.. codestrOm helped me with that.
It now fails at a point where we can proceed once heimdal is rebuilt
(my other mail on dh_shlibdeps).
I have a high level of interest in possibly helping with the
krb5/heimdal as it's something on my eventual TODO list.. I've talked
Erast Benson wrote:
Very interesting development!
snip /
I like the idea of modular approach to build ON. I do believe that
kernel, libc, networking all could be delivered as separate component
rather than monolitic jumbo tar drop...
And yes, we need to drop closed bins right from the start,