My own inputs within

On Tue, Nov 9, 2010 at 7:51 PM, Moinak Ghosh <[email protected]> wrote:
> On Sat, Nov 6, 2010 at 8:50 PM, USM Bish <[email protected]> wrote:
>>
>> I really  do not know, if  you really need a  "binary package"
>> based approach. The  issue is the variability  of hardware use
>> here. I have  nothing against "rpm" or  "dpkg" based approach,
>> but then,  at the end  of the  day, Belenix would  become "Yet
>> Another Distro" ! Since the userland  s/w is same for all *nix
>> based OSs, nobody would appreciate the difference.
>>

Yes, we could indeed become Yet Another Distro. Given that the core
team often has little time to stay abreast of package versions, it
becomes useful for us to use the OpenIndiana team's efforts, to
contribute spec file fixes there, and to focus on other
differentiating factors such as installers, package managers, system
tools, moving to more bleeding edge kernels from illumos as compared
to OpenIndiana, etc.

>> I  found nothing  wrong with  the "specs"  based system  which
>> Moinak had used for the  initial belenix development. This can
>> be easily extended  to a source based  distribution system. My
>> preference  would always  be  for a  source based  technology,
>> rather than  pre-compiled binary downloads.  Anything compiled
>> on your box always works !
>>

We'll continue to use spec files where needed. The spec files that
we've been using so far, are spec files that have all the elemets that
rpm supports as well as some elements that have been specific to the
pkgbuild build system.

Moinak has proposed that we treat OpenIndiana as our upstream, import
binaries from within the IPS files into RPM files, and then use those
RPM files.

<snip/>
>
>   Having said this we definitely want source build to be a reality for
>   those who want to experiment. It may even be an excellent way
>   to build and install Multimedia related software with machine
>   specific optimizations. Having a source build install is also related
>   to a future effort within the OpenIndiana community to unify build
>   systems to a common system, logically spec files as of now.
>

In fact, with the spec files and the rpmbuild build in place, one
could consider modifying ports or portage to pull in specs and
rpmbuild into the destination folders.

<snip/>

>> Now that Oracle  has pulled the plug on  OpenSolaris, a larger
>> community support is needed if any fork of the old OpenSolaris
>> base is to continue.
>>
>
>   Yes, this is already  happening around Illumos and OpenIndiana
>   efforts and we should gather around those and contribute to the
>   common goal.
>

Based on the outcome of this discussion, we'll be talking about the
Belenix goals on the OpenIndiana lists.

> Regards,
> Moinak.
> --

-- Sriram
_______________________________________________
belenix-discuss mailing list
http://mail.opensolaris.org/mailman/listinfo/belenix-discuss
http://groups.google.com/group/belenix-discuss

Reply via email to