[OpenIndiana-discuss] Making OI Packages (part I)
Søren Krarup Olesen
sko at es.aau.dk
Fri Oct 29 16:33:38 UTC 2010
As you may know, I am a newbie to OI--less so to Solaris, where I typed
in my first C-programs in vi with nothing but an ASCII terminal...those
were the days--and those days lasted for years in my case ;-)
Now, there is a couple of questions regarding the making packages or
the mere problem of porting things to OI, something that I am really
eager to do, if I only knew how...
You see, it's not so much about compiling things and make them work,
it's more what rules to follow:
1) Some packages are named sunw...followed by a name. What does that
really mean? sun is referring to Sun obviously but what about the 'w'?
2) How do we differ between run-time libs and development "libs" (the
latter typically just a single .h file) when it comes to *naming*?
Under Linux/Debian it was simple, e.g.: bananasplit.deb and bananasplit
3) Must I in a compiled package include GNU license + source or will
the binaries suffice?
4) Must I provide compiled packages with both gcc and CC, is there some
kind of preference? And what names should be used?
5) Same as 4) only how to differ between 32 bits and 64 bits. And
again...the naming question.
I have many more, but it's time to make some Friday evening supper now,
so let's keep it like this.
More information about the OpenIndiana-discuss