From moinakg at gmail.com  Wed Jun 11 09:44:04 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Wed, 11 Jun 2008 22:14:04 +0530
Subject: [belenix-dev] Update on 0.7.1
Message-ID: <46fe20470806110944m165a1585j4c1af70fc0e23e1a@mail.gmail.com>

Hi Folks,

   Thought it is a good time to socialize what's up with work on the
0.7.1 release.
Right now progress on the new website is a little slow with several of us busy.

I have built ON B90 and new FOX sources and using a base set of packages from
the existing BeleniX release I have created a chroot environment where
it is possible
to compile stuff. I am currently building the SFW consolidation within
that chroot
environment. Subsequently I will be upgrading various packages in the BeleniX
spec files repository to newer versions and also upgrade to KDE 3.5.9 and build
all of those.

Once these things are done we will have a new set of packages using which I
can generate a new ISO and start testing it. I will also post a test
version of the
ISO for others to try out.

We will be tackling the various bugs and RFE after all these builds are done.
One of the things that people can help out with is to update the BeleniX spec
files to newer versions. In additions new artwork like wallpapers, suggested
themes etc. are welcome.

One major work will be to build the slim_install repository and re-brand the
Caiman installer. This task is made difficult since most of the strings are
hardcoded and scattered all over the source files. Ideally these should all be
macros in a single header file. Can someone help with modifying Caiman
sources to collect all strings as macros in a single header ? The task should
be straightforward if a little tedious - maybe some scripting can help. We can
then submit a bug against Caiman and propose this patch on indiana-discuss.
This is important to allow other distros to easily re-brand Caiman and use it.

Finally GNOME 2.22 (JDS) will also have to be built. I will start pushing the
packages to the BeleniX package repository server as and when I have them
built. These will still be in the form of SVR4 packages installable via pkg-get
as IPS work will take some time. IMHO IPS still has a bunch of problems
and areas of improvement that need addressing before it can be generally
used. Lack of an on-disk format and mirroring are some things I personally
consider impt. limitations.

Of course I have missed or glossed over more work that needs to be done.

Regards,
Moinak.


From sriramnrn at gmail.com  Wed Jun 11 13:17:38 2008
From: sriramnrn at gmail.com (Sriram Narayanan)
Date: Thu, 12 Jun 2008 01:47:38 +0530
Subject: [belenix-dev] [belenix-discuss] Update on 0.7.1
In-Reply-To: <46fe20470806110944m165a1585j4c1af70fc0e23e1a@mail.gmail.com>
References: <46fe20470806110944m165a1585j4c1af70fc0e23e1a@mail.gmail.com>
Message-ID: <49977f270806111317g352313aex3a089a809efec033@mail.gmail.com>

I'm going to play the role of the newbie here :P

On Wed, Jun 11, 2008 at 10:14 PM, Moinak Ghosh <moinakg at gmail.com> wrote:
> Hi Folks,
>
>   Thought it is a good time to socialize what's up with work on the
> 0.7.1 release.
> Right now progress on the new website is a little slow with several of us busy.
>
> I have built ON B90 and new FOX sources and using a base set of packages from
> the existing BeleniX release I have created a chroot environment where
> it is possible
> to compile stuff.

I assume you mean that I could use any existing opensolaris / solaris
setup (say build 81//belenix 0.7), follow your chroot instructions and
then go about building somethin from a much later revision (build 90
in this case).

Could you post the instructions for creating a chroot, please ?


> I am currently building the SFW consolidation within
> that chroot
> environment. Subsequently I will be upgrading various packages in the BeleniX
> spec files repository to newer versions and also upgrade to KDE 3.5.9 and build
> all of those.
>


One this to ensure would be that we use SFE where available. I'd
recently spotted a minor issue where SFEwine had a dependency on
SFWlcms. There was already an SFElcms on Belenix, but wine wouldn't
build because SFWlcms was missing.

I think the only way to spot such issues would be to build SFE on
Belenix 0.7 once. Shive has been telling me this and I have started to
follow this advice.

> Once these things are done we will have a new set of packages using which I
> can generate a new ISO and start testing it. I will also post a test
> version of the
> ISO for others to try out.
>

Ideally, with the steps taken to create all this.

> We will be tackling the various bugs and RFE after all these builds are done.

I'm wondering if moving from build 81 to build 90 is justifiable in a
move from 0.7 to 0.7.1

It should be OK, of course, but it's just that the minor revision
number change doesn't indiciate a a change in the underlying ON
revision.

> One of the things that people can help out with is to update the BeleniX spec
> files to newer versions.

Moinak, would it be OK to build within Belenix 0.7 itself, given that
we're moving ON from build 81 to build 90.

I faced a curious problem recently. On SXDE build 81, I was able to
build and run vpnc 0.5.1. While I was able to successfully build vpnc
on belenix 0.7 (based on build 81), I was unable to run it. There some
issue with a missing "ip" command, I think. This is a separate topic,
of course, but I want to ask if the following makes sense.

- Build SFE end to end on Belenix 0.7
- Move to newer version where possible.

Now here is where I get stuck. I could build stuff on Belenix 0.7, but
the only way to validate that all this will work on build 90 would be
to actually try it out on a build 90. And would that then be an early
Belenix 0.7.1 that you would put out ?

In which case, the following is what I can think of:
- Take a prelim build 90 based 0.7.1 and build the SFE end to end on that.
- Put out yet another 0.7.1 based on the revised packages and test again.

>  In additions new artwork like wallpapers, suggested
> themes etc. are welcome.
>

Gilberto could play an important role here, I think.

> One major work will be to build the slim_install repository and re-brand the
> Caiman installer. This task is made difficult since most of the strings are
> hardcoded and scattered all over the source files. Ideally these should all be
> macros in a single header file. Can someone help with modifying Caiman
> sources to collect all strings as macros in a single header ? The task should
> be straightforward if a little tedious - maybe some scripting can help. We can
> then submit a bug against Caiman and propose this patch on indiana-discuss.
> This is important to allow other distros to easily re-brand Caiman and use it.
>

Sounds good. Pathches in the bug tracker seem to be the way to go :)

> Finally GNOME 2.22 (JDS) will also have to be built. I will start pushing the
> packages to the BeleniX package repository server as and when I have them
> built. These will still be in the form of SVR4 packages installable via pkg-get
> as IPS work will take some time.


> IMHO IPS still has a bunch of problems
> and areas of improvement that need addressing before it can be generally
> used. Lack of an on-disk format and mirroring are some things I personally
> consider impt. limitations.
>

Well, given that one can still install pkgs on even opensolaris
2008.5, it seems fine that we stick to svr4 for now and pay attention
to IPS some time later. No point in fixing IPS when Belenix itself
needs out love and care !

> Of course I have missed or glossed over more work that needs to be done.
>
Some that I can think of:
- Network repository
- storage for sources mentioned in the spec files
- Fixes to Belenix 0.7 such that it can build stuff.
   An important one that I can think of is the lsymlink from
aclocal1.10 to aclocal

> Regards,
> Moinak.
> _______________________________________________
> belenix-discuss mailing list
> http://mail.opensolaris.org/mailman/listinfo/belenix-discuss
> http://groups.google.com/group/belenix-discuss
>


From moinakg at gmail.com  Thu Jun 12 10:19:04 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Thu, 12 Jun 2008 22:49:04 +0530
Subject: [belenix-dev] [belenix-discuss] Update on 0.7.1
In-Reply-To: <49977f270806111317g352313aex3a089a809efec033@mail.gmail.com>
References: <46fe20470806110944m165a1585j4c1af70fc0e23e1a@mail.gmail.com>
	<49977f270806111317g352313aex3a089a809efec033@mail.gmail.com>
Message-ID: <46fe20470806121019s5d65207lc90b21c3599cfde8@mail.gmail.com>

On Thu, Jun 12, 2008 at 1:47 AM, Sriram Narayanan <sriramnrn at gmail.com> wrote:
> I'm going to play the role of the newbie here :P
>
> On Wed, Jun 11, 2008 at 10:14 PM, Moinak Ghosh <moinakg at gmail.com> wrote:
>> Hi Folks,
>>
>>   Thought it is a good time to socialize what's up with work on the
>> 0.7.1 release.
>> Right now progress on the new website is a little slow with several of us busy.
>>
>> I have built ON B90 and new FOX sources and using a base set of packages from
>> the existing BeleniX release I have created a chroot environment where
>> it is possible
>> to compile stuff.
>
> I assume you mean that I could use any existing opensolaris / solaris
> setup (say build 81//belenix 0.7), follow your chroot instructions and
> then go about building somethin from a much later revision (build 90
> in this case).
>
> Could you post the instructions for creating a chroot, please ?

   Yes hold on. I will post stuff on my blog.

>
>
>> I am currently building the SFW consolidation within
>> that chroot
>> environment. Subsequently I will be upgrading various packages in the BeleniX
>> spec files repository to newer versions and also upgrade to KDE 3.5.9 and build
>> all of those.
>>
>
>
> One this to ensure would be that we use SFE where available. I'd
> recently spotted a minor issue where SFEwine had a dependency on
> SFWlcms. There was already an SFElcms on Belenix, but wine wouldn't
> build because SFWlcms was missing.
>
> I think the only way to spot such issues would be to build SFE on
> Belenix 0.7 once. Shive has been telling me this and I have started to
> follow this advice.
>

   Yes. In addition all the SFW gate stuff has to be converted into SPEC
   files in the BeleniX repo and regularly synced up with SFW changes
   going forward. The BeleniX repo has to be self-contained. This is also
   impt when we do all the package name refactoring.

>> Once these things are done we will have a new set of packages using which I
>> can generate a new ISO and start testing it. I will also post a test
>> version of the
>> ISO for others to try out.
>>
>
> Ideally, with the steps taken to create all this.
>
>> We will be tackling the various bugs and RFE after all these builds are done.
>
> I'm wondering if moving from build 81 to build 90 is justifiable in a
> move from 0.7 to 0.7.1

   I think it should be fine. the base OS should be updated to get better
   and more drivers, ATI 3D support etc. Otherwise the distro becomes
   quite outdated as OpenSolaris builds keep moving quite fast.

>
> It should be OK, of course, but it's just that the minor revision
> number change doesn't indiciate a a change in the underlying ON
> revision.

   That is why we have the release notes.

>
>> One of the things that people can help out with is to update the BeleniX spec
>> files to newer versions.
>
> Moinak, would it be OK to build within Belenix 0.7 itself, given that
> we're moving ON from build 81 to build 90.
>

   Should be fine.

> I faced a curious problem recently. On SXDE build 81, I was able to
> build and run vpnc 0.5.1. While I was able to successfully build vpnc
> on belenix 0.7 (based on build 81), I was unable to run it. There some
> issue with a missing "ip" command, I think. This is a separate topic,
> of course, but I want to ask if the following makes sense.

   Probably some additional package missing. Default install of 0.7
   does not contain all ON packages.

>
> - Build SFE end to end on Belenix 0.7
> - Move to newer version where possible.

   Yes does make very good sense.

>
> Now here is where I get stuck. I could build stuff on Belenix 0.7, but
> the only way to validate that all this will work on build 90 would be
> to actually try it out on a build 90. And would that then be an early
> Belenix 0.7.1 that you would put out ?

   Yes.

>
> In which case, the following is what I can think of:
> - Take a prelim build 90 based 0.7.1 and build the SFE end to end on that.
> - Put out yet another 0.7.1 based on the revised packages and test again.
>
>>  In additions new artwork like wallpapers, suggested
>> themes etc. are welcome.
>>
>
> Gilberto could play an important role here, I think.

   Yes of course. And we need him to review the various user-interfaces.
   Let him boot the livecd once and perform an install in say VBox and
   provide feedback/suggestions about the various aspects.

>
>> One major work will be to build the slim_install repository and re-brand the
>> Caiman installer. This task is made difficult since most of the strings are
>> hardcoded and scattered all over the source files. Ideally these should all be
>> macros in a single header file. Can someone help with modifying Caiman
>> sources to collect all strings as macros in a single header ? The task should
>> be straightforward if a little tedious - maybe some scripting can help. We can
>> then submit a bug against Caiman and propose this patch on indiana-discuss.
>> This is important to allow other distros to easily re-brand Caiman and use it.
>>
>
> Sounds good. Pathches in the bug tracker seem to be the way to go :)
>
>> Finally GNOME 2.22 (JDS) will also have to be built. I will start pushing the
>> packages to the BeleniX package repository server as and when I have them
>> built. These will still be in the form of SVR4 packages installable via pkg-get
>> as IPS work will take some time.
>
>
>> IMHO IPS still has a bunch of problems
>> and areas of improvement that need addressing before it can be generally
>> used. Lack of an on-disk format and mirroring are some things I personally
>> consider impt. limitations.
>>
>
> Well, given that one can still install pkgs on even opensolaris
> 2008.5, it seems fine that we stick to svr4 for now and pay attention
> to IPS some time later. No point in fixing IPS when Belenix itself
> needs out love and care !

   Yes.

>
>> Of course I have missed or glossed over more work that needs to be done.
>>
> Some that I can think of:
> - Network repository
> - storage for sources mentioned in the spec files
> - Fixes to Belenix 0.7 such that it can build stuff.
>   An important one that I can think of is the lsymlink from
> aclocal1.10 to aclocal

   In additon symlink from automake to automake-1.10 and
   symlink from /usr/jdk/instances/jdk1.5.0 to
/usr/jdk/instances/jdk1.5.0_<minor>

Regards,
Moinak.

>
>> Regards,
>> Moinak.
>> _______________________________________________
>> belenix-discuss mailing list
>> http://mail.opensolaris.org/mailman/listinfo/belenix-discuss
>> http://groups.google.com/group/belenix-discuss
>>
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>


From shivakumar.gn at gmail.com  Thu Jun 12 18:33:32 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Fri, 13 Jun 2008 07:03:32 +0530
Subject: [belenix-dev] [belenix-discuss] Update on 0.7.1
In-Reply-To: <49977f270806111317g352313aex3a089a809efec033@mail.gmail.com>
References: <46fe20470806110944m165a1585j4c1af70fc0e23e1a@mail.gmail.com>
	<49977f270806111317g352313aex3a089a809efec033@mail.gmail.com>
Message-ID: <319ee2b10806121833v7dcf5b6am9e8bbdb2a509a80a@mail.gmail.com>

On Thu, Jun 12, 2008 at 1:47 AM, Sriram Narayanan <sriramnrn at gmail.com> wrote:
>
> On Wed, Jun 11, 2008 at 10:14 PM, Moinak Ghosh <moinakg at gmail.com> wrote:
>>
>> I have built ON B90 and new FOX sources and using a base set of packages from
>> the existing BeleniX release I have created a chroot environment where
>> it is possible
>> to compile stuff.
>
> I assume you mean that I could use any existing opensolaris / solaris
> setup (say build 81//belenix 0.7), follow your chroot instructions and
> then go about building somethin from a much later revision (build 90
> in this case).
>

You cannot use belenix 0.7 to build ON. I attempted it on Indiana for
ON(b90) which didn't succeed after fixing some of the dependencies.
Using SX was quicker way to get things to work for now, so I moved to
SX.
To build spec files and contribute one doesn't need a chroot, current
V0.7 is sufficient.
Chroot would be necessary for the 1st pass build or the 1st alpha release.

>
> Moinak, would it be OK to build within Belenix 0.7 itself, given that
> we're moving ON from build 81 to build 90.
>

B81 to B90 should make no difference to top application layers in
BeleniX. It is perfectly alright.

> I faced a curious problem recently. On SXDE build 81, I was able to
> build and run vpnc 0.5.1. While I was able to successfully build vpnc
> on belenix 0.7 (based on build 81), I was unable to run it. There some
> issue with a missing "ip" command, I think. This is a separate topic,
> of course, but I want to ask if the following makes sense.
>

Open a new thread & lets have a look at the error log.

>
> Now here is where I get stuck. I could build stuff on Belenix 0.7, but
> the only way to validate that all this will work on build 90

B81 to B90 move is a non-issue for applications. If anything it only
provides some more functionalities that the newer kernel provides and
a few bug fixes.
If apps start to break, it is an interface issue that shouldn't occur !
There could be issues with package dependencies (at spec file build
level), but an already built package on V0.7 is expected to work on
V0.7.1 at a binary level.

>
>> One major work will be to build the slim_install repository and re-brand the
>> Caiman installer.
>

I will look into this.

>
>> IMHO IPS still has a bunch of problems
>> and areas of improvement that need addressing before it can be generally
>> used. Lack of an on-disk format and mirroring are some things I personally
>> consider impt. limitations.
>>
>
> Well, given that one can still install pkgs on even opensolaris
> 2008.5, it seems fine that we stick to svr4 for now and pay attention
> to IPS some time later.
>

Zones support for packaging is not available with current packaging in
V0.7. We will need minor enhancements to SVR4 packaging utilities for
understanding zones on the lines of support available in live upgrade
in SX. With IPS this should work but there are other limitations as
pointed out.

-Shiv


From sriramnrn at gmail.com  Fri Jun 13 02:54:05 2008
From: sriramnrn at gmail.com (Sriram Narayanan)
Date: Fri, 13 Jun 2008 15:24:05 +0530
Subject: [belenix-dev] [belenix-discuss] Update on 0.7.1
In-Reply-To: <319ee2b10806121833v7dcf5b6am9e8bbdb2a509a80a@mail.gmail.com>
References: <46fe20470806110944m165a1585j4c1af70fc0e23e1a@mail.gmail.com>
	<49977f270806111317g352313aex3a089a809efec033@mail.gmail.com>
	<319ee2b10806121833v7dcf5b6am9e8bbdb2a509a80a@mail.gmail.com>
Message-ID: <49977f270806130254n47984876ie7e2e17b0cda4566@mail.gmail.com>

On Fri, Jun 13, 2008 at 7:03 AM, S h i v <shivakumar.gn at gmail.com> wrote:
>
> You cannot use belenix 0.7 to build ON. I attempted it on Indiana for
> ON(b90) which didn't succeed after fixing some of the dependencies.
> Using SX was quicker way to get things to work for now, so I moved to
> SX.
> To build spec files and contribute one doesn't need a chroot, current
> V0.7 is sufficient.

As you are aware, Belenix 0.7 didn't happen to have everything needed
for a pure Belenix based build of even the Belenix SE repository. This
is why I asked.

I think that at the moment, it's just Moinak who has the chroot
environment and that the more of us who have the same environment, the
better it'd be for building and testing. (I'm eagerly waiting for the
results of your buidl progress, btw - another blog post, perhaps ?)

> Chroot would be necessary for the 1st pass build or the 1st alpha release.
>
Ack. This is the chroot that I was talking about.

>>
>> Moinak, would it be OK to build within Belenix 0.7 itself, given that
>> we're moving ON from build 81 to build 90.
>>
>
> B81 to B90 should make no difference to top application layers in
> BeleniX. It is perfectly alright.
>

I spoke to Moinak about this. He reminded me that unlike the Linux
world where lots of things change every now and then, the API
stability guarantee in the Solaris world addresss this concern.

As a Gentoo user and distro constructor, I am quite used to things
breaking every now and then, and of having to rebuild vast eco systems
of various platforms on a Gentoo box.

Given that I have to be reminded of Solaris API stability, I
definitely need to set aside the Linux world experiences ! :)

>> I faced a curious problem recently. On SXDE build 81, I was able to
>> build and run vpnc 0.5.1. While I was able to successfully build vpnc
>> on belenix 0.7 (based on build 81), I was unable to run it. There some
>> issue with a missing "ip" command, I think. This is a separate topic,
>> of course, but I want to ask if the following makes sense.
>>
>
> Open a new thread & lets have a look at the error log.
>
Ack. This seems to be a difference in the packages that Belenix 0.7
and SXDE have. I'll send a package list when I again boot into
Belenix.

> If apps start to break, it is an interface issue that shouldn't occur !

Lol !

As written above, this will take some time to get used to :)

-- Sriram


From manishchaks at gmail.com  Fri Jun 13 03:18:58 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Fri, 13 Jun 2008 15:48:58 +0530
Subject: [belenix-dev] [belenix-discuss] Update on 0.7.1
In-Reply-To: <49977f270806130254n47984876ie7e2e17b0cda4566@mail.gmail.com>
References: <46fe20470806110944m165a1585j4c1af70fc0e23e1a@mail.gmail.com>
	<49977f270806111317g352313aex3a089a809efec033@mail.gmail.com>
	<319ee2b10806121833v7dcf5b6am9e8bbdb2a509a80a@mail.gmail.com>
	<49977f270806130254n47984876ie7e2e17b0cda4566@mail.gmail.com>
Message-ID: <142FD5D7-82E5-4831-BD10-E5EF8198AE13@gmail.com>

>
>> Chroot would be necessary for the 1st pass build or the 1st alpha  
>> release.
>>
> Ack. This is the chroot that I was talking about.
Looking forward to learning about and trying out the chroot environment,

Moinak:
Could you show us a five-min demo if time permits?

Shiv:
Can this be added to the agenda for the BOSUG meet?



From maybird1776 at yahoo.com  Fri Jun 13 06:24:22 2008
From: maybird1776 at yahoo.com (ken mays)
Date: Fri, 13 Jun 2008 06:24:22 -0700 (PDT)
Subject: [belenix-dev] [belenix-discuss] Update on 0.7.1
In-Reply-To: <46fe20470806121019s5d65207lc90b21c3599cfde8@mail.gmail.com>
Message-ID: <360679.52380.qm@web34207.mail.mud.yahoo.com>

Can there be an update request for the FOX build for Belenix 0.7.1 that we use Mesa 7.0.3?? This will very helpful for those of us into video driver review and Xorg...

~K


--- On Thu, 6/12/08, Moinak Ghosh <moinakg at gmail.com> wrote:

> From: Moinak Ghosh <moinakg at gmail.com>
> Subject: Re: [belenix-dev] [belenix-discuss] Update on 0.7.1
> To: "Sriram Narayanan" <sriramnrn at gmail.com>
> Cc: "Belenix Developers" <belenix-dev at opensolaris.org>, "Belenix Discuss" <belenix-discuss at opensolaris.org>
> Date: Thursday, June 12, 2008, 1:19 PM
> On Thu, Jun 12, 2008 at 1:47 AM, Sriram Narayanan
> <sriramnrn at gmail.com> wrote:
> > I'm going to play the role of the newbie here :P
> >
> > On Wed, Jun 11, 2008 at 10:14 PM, Moinak Ghosh
> <moinakg at gmail.com> wrote:
> >> Hi Folks,
> >>
> >>   Thought it is a good time to socialize
> what's up with work on the
> >> 0.7.1 release.
> >> Right now progress on the new website is a little
> slow with several of us busy.
> >>
> >> I have built ON B90 and new FOX sources and using
> a base set of packages from
> >> the existing BeleniX release I have created a
> chroot environment where
> >> it is possible
> >> to compile stuff.
> >
> > I assume you mean that I could use any existing
> opensolaris / solaris
> > setup (say build 81//belenix 0.7), follow your chroot
> instructions and
> > then go about building somethin from a much later
> revision (build 90
> > in this case).
> >
> > Could you post the instructions for creating a chroot,
> please ?
> 
>    Yes hold on. I will post stuff on my blog.
> 
> >
> >
> >> I am currently building the SFW consolidation
> within
> >> that chroot
> >> environment. Subsequently I will be upgrading
> various packages in the BeleniX
> >> spec files repository to newer versions and also
> upgrade to KDE 3.5.9 and build
> >> all of those.
> >>
> >
> >
> > One this to ensure would be that we use SFE where
> available. I'd
> > recently spotted a minor issue where SFEwine had a
> dependency on
> > SFWlcms. There was already an SFElcms on Belenix, but
> wine wouldn't
> > build because SFWlcms was missing.
> >
> > I think the only way to spot such issues would be to
> build SFE on
> > Belenix 0.7 once. Shive has been telling me this and I
> have started to
> > follow this advice.
> >
> 
>    Yes. In addition all the SFW gate stuff has to be
> converted into SPEC
>    files in the BeleniX repo and regularly synced up with
> SFW changes
>    going forward. The BeleniX repo has to be
> self-contained. This is also
>    impt when we do all the package name refactoring.
> 
> >> Once these things are done we will have a new set
> of packages using which I
> >> can generate a new ISO and start testing it. I
> will also post a test
> >> version of the
> >> ISO for others to try out.
> >>
> >
> > Ideally, with the steps taken to create all this.
> >
> >> We will be tackling the various bugs and RFE after
> all these builds are done.
> >
> > I'm wondering if moving from build 81 to build 90
> is justifiable in a
> > move from 0.7 to 0.7.1
> 
>    I think it should be fine. the base OS should be updated
> to get better
>    and more drivers, ATI 3D support etc. Otherwise the
> distro becomes
>    quite outdated as OpenSolaris builds keep moving quite
> fast.
> 
> >
> > It should be OK, of course, but it's just that the
> minor revision
> > number change doesn't indiciate a a change in the
> underlying ON
> > revision.
> 
>    That is why we have the release notes.
> 
> >
> >> One of the things that people can help out with is
> to update the BeleniX spec
> >> files to newer versions.
> >
> > Moinak, would it be OK to build within Belenix 0.7
> itself, given that
> > we're moving ON from build 81 to build 90.
> >
> 
>    Should be fine.
> 
> > I faced a curious problem recently. On SXDE build 81,
> I was able to
> > build and run vpnc 0.5.1. While I was able to
> successfully build vpnc
> > on belenix 0.7 (based on build 81), I was unable to
> run it. There some
> > issue with a missing "ip" command, I think.
> This is a separate topic,
> > of course, but I want to ask if the following makes
> sense.
> 
>    Probably some additional package missing. Default
> install of 0.7
>    does not contain all ON packages.
> 
> >
> > - Build SFE end to end on Belenix 0.7
> > - Move to newer version where possible.
> 
>    Yes does make very good sense.
> 
> >
> > Now here is where I get stuck. I could build stuff on
> Belenix 0.7, but
> > the only way to validate that all this will work on
> build 90 would be
> > to actually try it out on a build 90. And would that
> then be an early
> > Belenix 0.7.1 that you would put out ?
> 
>    Yes.
> 
> >
> > In which case, the following is what I can think of:
> > - Take a prelim build 90 based 0.7.1 and build the SFE
> end to end on that.
> > - Put out yet another 0.7.1 based on the revised
> packages and test again.
> >
> >>  In additions new artwork like wallpapers,
> suggested
> >> themes etc. are welcome.
> >>
> >
> > Gilberto could play an important role here, I think.
> 
>    Yes of course. And we need him to review the various
> user-interfaces.
>    Let him boot the livecd once and perform an install in
> say VBox and
>    provide feedback/suggestions about the various aspects.
> 
> >
> >> One major work will be to build the slim_install
> repository and re-brand the
> >> Caiman installer. This task is made difficult
> since most of the strings are
> >> hardcoded and scattered all over the source files.
> Ideally these should all be
> >> macros in a single header file. Can someone help
> with modifying Caiman
> >> sources to collect all strings as macros in a
> single header ? The task should
> >> be straightforward if a little tedious - maybe
> some scripting can help. We can
> >> then submit a bug against Caiman and propose this
> patch on indiana-discuss.
> >> This is important to allow other distros to easily
> re-brand Caiman and use it.
> >>
> >
> > Sounds good. Pathches in the bug tracker seem to be
> the way to go :)
> >
> >> Finally GNOME 2.22 (JDS) will also have to be
> built. I will start pushing the
> >> packages to the BeleniX package repository server
> as and when I have them
> >> built. These will still be in the form of SVR4
> packages installable via pkg-get
> >> as IPS work will take some time.
> >
> >
> >> IMHO IPS still has a bunch of problems
> >> and areas of improvement that need addressing
> before it can be generally
> >> used. Lack of an on-disk format and mirroring are
> some things I personally
> >> consider impt. limitations.
> >>
> >
> > Well, given that one can still install pkgs on even
> opensolaris
> > 2008.5, it seems fine that we stick to svr4 for now
> and pay attention
> > to IPS some time later. No point in fixing IPS when
> Belenix itself
> > needs out love and care !
> 
>    Yes.
> 
> >
> >> Of course I have missed or glossed over more work
> that needs to be done.
> >>
> > Some that I can think of:
> > - Network repository
> > - storage for sources mentioned in the spec files
> > - Fixes to Belenix 0.7 such that it can build stuff.
> >   An important one that I can think of is the lsymlink
> from
> > aclocal1.10 to aclocal
> 
>    In additon symlink from automake to automake-1.10 and
>    symlink from /usr/jdk/instances/jdk1.5.0 to
> /usr/jdk/instances/jdk1.5.0_<minor>
> 
> Regards,
> Moinak.
> 
> >
> >> Regards,
> >> Moinak.
> >> _______________________________________________
> >> belenix-discuss mailing list
> >>
> http://mail.opensolaris.org/mailman/listinfo/belenix-discuss
> >> http://groups.google.com/group/belenix-discuss
> >>
> > _______________________________________________
> > belenix-dev mailing list
> > belenix-dev at opensolaris.org
> >
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
> >
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev


      


From moinakg at gmail.com  Fri Jun 13 08:18:56 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Fri, 13 Jun 2008 20:48:56 +0530
Subject: [belenix-dev] [belenix-discuss] Update on 0.7.1
In-Reply-To: <360679.52380.qm@web34207.mail.mud.yahoo.com>
References: <46fe20470806121019s5d65207lc90b21c3599cfde8@mail.gmail.com>
	<360679.52380.qm@web34207.mail.mud.yahoo.com>
Message-ID: <46fe20470806130818u2caf8e21jf1b8caee0047332b@mail.gmail.com>

On Fri, Jun 13, 2008 at 6:54 PM, ken mays <maybird1776 at yahoo.com> wrote:
> Can there be an update request for the FOX build for Belenix 0.7.1 that we use Mesa 7.0.3?? This will very helpful for those of us into video driver review and Xorg...

   It will be really nice to upgrade Mesa, but that requires some
porting work to
   get the Solaris dri stuff working with the new Mesa. This is non-trivial and
   I think is being worked on by the SUN china folks. AlanC should have more
   updates.

Regards,
Moinak.

>
> ~K
>
>
> --- On Thu, 6/12/08, Moinak Ghosh <moinakg at gmail.com> wrote:
>
>> From: Moinak Ghosh <moinakg at gmail.com>
>> Subject: Re: [belenix-dev] [belenix-discuss] Update on 0.7.1
>> To: "Sriram Narayanan" <sriramnrn at gmail.com>
>> Cc: "Belenix Developers" <belenix-dev at opensolaris.org>, "Belenix Discuss" <belenix-discuss at opensolaris.org>
>> Date: Thursday, June 12, 2008, 1:19 PM
>> On Thu, Jun 12, 2008 at 1:47 AM, Sriram Narayanan
>> <sriramnrn at gmail.com> wrote:
>> > I'm going to play the role of the newbie here :P
>> >
>> > On Wed, Jun 11, 2008 at 10:14 PM, Moinak Ghosh
>> <moinakg at gmail.com> wrote:
>> >> Hi Folks,
>> >>
>> >>   Thought it is a good time to socialize
>> what's up with work on the
>> >> 0.7.1 release.
>> >> Right now progress on the new website is a little
>> slow with several of us busy.
>> >>
>> >> I have built ON B90 and new FOX sources and using
>> a base set of packages from
>> >> the existing BeleniX release I have created a
>> chroot environment where
>> >> it is possible
>> >> to compile stuff.
>> >
>> > I assume you mean that I could use any existing
>> opensolaris / solaris
>> > setup (say build 81//belenix 0.7), follow your chroot
>> instructions and
>> > then go about building somethin from a much later
>> revision (build 90
>> > in this case).
>> >
>> > Could you post the instructions for creating a chroot,
>> please ?
>>
>>    Yes hold on. I will post stuff on my blog.
>>
>> >
>> >
>> >> I am currently building the SFW consolidation
>> within
>> >> that chroot
>> >> environment. Subsequently I will be upgrading
>> various packages in the BeleniX
>> >> spec files repository to newer versions and also
>> upgrade to KDE 3.5.9 and build
>> >> all of those.
>> >>
>> >
>> >
>> > One this to ensure would be that we use SFE where
>> available. I'd
>> > recently spotted a minor issue where SFEwine had a
>> dependency on
>> > SFWlcms. There was already an SFElcms on Belenix, but
>> wine wouldn't
>> > build because SFWlcms was missing.
>> >
>> > I think the only way to spot such issues would be to
>> build SFE on
>> > Belenix 0.7 once. Shive has been telling me this and I
>> have started to
>> > follow this advice.
>> >
>>
>>    Yes. In addition all the SFW gate stuff has to be
>> converted into SPEC
>>    files in the BeleniX repo and regularly synced up with
>> SFW changes
>>    going forward. The BeleniX repo has to be
>> self-contained. This is also
>>    impt when we do all the package name refactoring.
>>
>> >> Once these things are done we will have a new set
>> of packages using which I
>> >> can generate a new ISO and start testing it. I
>> will also post a test
>> >> version of the
>> >> ISO for others to try out.
>> >>
>> >
>> > Ideally, with the steps taken to create all this.
>> >
>> >> We will be tackling the various bugs and RFE after
>> all these builds are done.
>> >
>> > I'm wondering if moving from build 81 to build 90
>> is justifiable in a
>> > move from 0.7 to 0.7.1
>>
>>    I think it should be fine. the base OS should be updated
>> to get better
>>    and more drivers, ATI 3D support etc. Otherwise the
>> distro becomes
>>    quite outdated as OpenSolaris builds keep moving quite
>> fast.
>>
>> >
>> > It should be OK, of course, but it's just that the
>> minor revision
>> > number change doesn't indiciate a a change in the
>> underlying ON
>> > revision.
>>
>>    That is why we have the release notes.
>>
>> >
>> >> One of the things that people can help out with is
>> to update the BeleniX spec
>> >> files to newer versions.
>> >
>> > Moinak, would it be OK to build within Belenix 0.7
>> itself, given that
>> > we're moving ON from build 81 to build 90.
>> >
>>
>>    Should be fine.
>>
>> > I faced a curious problem recently. On SXDE build 81,
>> I was able to
>> > build and run vpnc 0.5.1. While I was able to
>> successfully build vpnc
>> > on belenix 0.7 (based on build 81), I was unable to
>> run it. There some
>> > issue with a missing "ip" command, I think.
>> This is a separate topic,
>> > of course, but I want to ask if the following makes
>> sense.
>>
>>    Probably some additional package missing. Default
>> install of 0.7
>>    does not contain all ON packages.
>>
>> >
>> > - Build SFE end to end on Belenix 0.7
>> > - Move to newer version where possible.
>>
>>    Yes does make very good sense.
>>
>> >
>> > Now here is where I get stuck. I could build stuff on
>> Belenix 0.7, but
>> > the only way to validate that all this will work on
>> build 90 would be
>> > to actually try it out on a build 90. And would that
>> then be an early
>> > Belenix 0.7.1 that you would put out ?
>>
>>    Yes.
>>
>> >
>> > In which case, the following is what I can think of:
>> > - Take a prelim build 90 based 0.7.1 and build the SFE
>> end to end on that.
>> > - Put out yet another 0.7.1 based on the revised
>> packages and test again.
>> >
>> >>  In additions new artwork like wallpapers,
>> suggested
>> >> themes etc. are welcome.
>> >>
>> >
>> > Gilberto could play an important role here, I think.
>>
>>    Yes of course. And we need him to review the various
>> user-interfaces.
>>    Let him boot the livecd once and perform an install in
>> say VBox and
>>    provide feedback/suggestions about the various aspects.
>>
>> >
>> >> One major work will be to build the slim_install
>> repository and re-brand the
>> >> Caiman installer. This task is made difficult
>> since most of the strings are
>> >> hardcoded and scattered all over the source files.
>> Ideally these should all be
>> >> macros in a single header file. Can someone help
>> with modifying Caiman
>> >> sources to collect all strings as macros in a
>> single header ? The task should
>> >> be straightforward if a little tedious - maybe
>> some scripting can help. We can
>> >> then submit a bug against Caiman and propose this
>> patch on indiana-discuss.
>> >> This is important to allow other distros to easily
>> re-brand Caiman and use it.
>> >>
>> >
>> > Sounds good. Pathches in the bug tracker seem to be
>> the way to go :)
>> >
>> >> Finally GNOME 2.22 (JDS) will also have to be
>> built. I will start pushing the
>> >> packages to the BeleniX package repository server
>> as and when I have them
>> >> built. These will still be in the form of SVR4
>> packages installable via pkg-get
>> >> as IPS work will take some time.
>> >
>> >
>> >> IMHO IPS still has a bunch of problems
>> >> and areas of improvement that need addressing
>> before it can be generally
>> >> used. Lack of an on-disk format and mirroring are
>> some things I personally
>> >> consider impt. limitations.
>> >>
>> >
>> > Well, given that one can still install pkgs on even
>> opensolaris
>> > 2008.5, it seems fine that we stick to svr4 for now
>> and pay attention
>> > to IPS some time later. No point in fixing IPS when
>> Belenix itself
>> > needs out love and care !
>>
>>    Yes.
>>
>> >
>> >> Of course I have missed or glossed over more work
>> that needs to be done.
>> >>
>> > Some that I can think of:
>> > - Network repository
>> > - storage for sources mentioned in the spec files
>> > - Fixes to Belenix 0.7 such that it can build stuff.
>> >   An important one that I can think of is the lsymlink
>> from
>> > aclocal1.10 to aclocal
>>
>>    In additon symlink from automake to automake-1.10 and
>>    symlink from /usr/jdk/instances/jdk1.5.0 to
>> /usr/jdk/instances/jdk1.5.0_<minor>
>>
>> Regards,
>> Moinak.
>>
>> >
>> >> Regards,
>> >> Moinak.
>> >> _______________________________________________
>> >> belenix-discuss mailing list
>> >>
>> http://mail.opensolaris.org/mailman/listinfo/belenix-discuss
>> >> http://groups.google.com/group/belenix-discuss
>> >>
>> > _______________________________________________
>> > belenix-dev mailing list
>> > belenix-dev at opensolaris.org
>> >
>> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>> >
>> _______________________________________________
>> belenix-dev mailing list
>> belenix-dev at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
>
>
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>


From moinakg at gmail.com  Fri Jun 13 09:07:37 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Fri, 13 Jun 2008 21:37:37 +0530
Subject: [belenix-dev] [belenix-discuss] Update on 0.7.1
In-Reply-To: <142FD5D7-82E5-4831-BD10-E5EF8198AE13@gmail.com>
References: <46fe20470806110944m165a1585j4c1af70fc0e23e1a@mail.gmail.com>
	<49977f270806111317g352313aex3a089a809efec033@mail.gmail.com>
	<319ee2b10806121833v7dcf5b6am9e8bbdb2a509a80a@mail.gmail.com>
	<49977f270806130254n47984876ie7e2e17b0cda4566@mail.gmail.com>
	<142FD5D7-82E5-4831-BD10-E5EF8198AE13@gmail.com>
Message-ID: <46fe20470806130907o31ff5597o545d87d9d33001df@mail.gmail.com>

On Fri, Jun 13, 2008 at 3:48 PM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
>>
>>> Chroot would be necessary for the 1st pass build or the 1st alpha
>>> release.
>>>
>> Ack. This is the chroot that I was talking about.
> Looking forward to learning about and trying out the chroot environment,
>
> Moinak:
> Could you show us a five-min demo if time permits?
>
> Shiv:
> Can this be added to the agenda for the BOSUG meet?

   It is quite simple. Since I am laptop-less at this time I can't give a demo.
   However I will put up some instructions on my blog.

Regards,
Moinak.

>
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>


From manishchaks at gmail.com  Fri Jun 13 09:09:45 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Fri, 13 Jun 2008 21:39:45 +0530
Subject: [belenix-dev] [belenix-discuss] Update on 0.7.1
In-Reply-To: <46fe20470806130907o31ff5597o545d87d9d33001df@mail.gmail.com>
References: <46fe20470806110944m165a1585j4c1af70fc0e23e1a@mail.gmail.com>
	<49977f270806111317g352313aex3a089a809efec033@mail.gmail.com>
	<319ee2b10806121833v7dcf5b6am9e8bbdb2a509a80a@mail.gmail.com>
	<49977f270806130254n47984876ie7e2e17b0cda4566@mail.gmail.com>
	<142FD5D7-82E5-4831-BD10-E5EF8198AE13@gmail.com>
	<46fe20470806130907o31ff5597o545d87d9d33001df@mail.gmail.com>
Message-ID: <EE1FCB20-7510-49C9-A692-B899BCB79AA1@gmail.com>


>>
>>
>
>   It is quite simple. Since I am laptop-less at this time I can't  
> give a demo.
>   However I will put up some instructions on my blog.
Thanks Moinak!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080613/cb28314e/attachment.html>

From avinashtjoshi at gmail.com  Sat Jun 14 00:16:46 2008
From: avinashtjoshi at gmail.com (Avinash Joshi)
Date: Sat, 14 Jun 2008 12:46:46 +0530
Subject: [belenix-dev] GUI doesnt seem to come up
Message-ID: <3af7c1a80806140016x4c399fc3q2cff8c7568ab13a7@mail.gmail.com>

Hi,

   I have installed opensolaris 5.11 build 86 on a sony VAIO VGNCR-35G
laptop. I am not getting the GUI. When  I tried


#/usr/X11/bin/Xorg -configure

and then
#/usr/X11/bin/Xorg -config xorg.conf.new

I get the screen with my mouse and keyboard detected but no display..

it says

(EE) Screen 0 is not dri capable



So, I tried disabling dri by commenting out the load dri in xorg.conf.new

still an error shows

screens found but none have a usable configuration

I tired deleting the .xorg.conf file in /etc/X11

Solaris 2008 works perfectly for me. I want to know how does it load the
graphics...
I tried creating the xorg.conf file in OpenSolaris 2008 and the GUI failed.
Buti could not find the xorg.conf file

I dont want 3d effects I just want the basic GUI

--
~ Avinash Joshi
http://avinashjoshi.co.in/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080614/a928baec/attachment.html>

From shivakumar.gn at gmail.com  Sun Jun 15 19:32:28 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Mon, 16 Jun 2008 08:02:28 +0530
Subject: [belenix-dev] [belenix-discuss] Update on 0.7.1
In-Reply-To: <46fe20470806110944m165a1585j4c1af70fc0e23e1a@mail.gmail.com>
References: <46fe20470806110944m165a1585j4c1af70fc0e23e1a@mail.gmail.com>
Message-ID: <319ee2b10806151932r25beefc5v535fc436a38e4881@mail.gmail.com>

On Wed, Jun 11, 2008 at 10:14 PM, Moinak Ghosh <moinakg at gmail.com> wrote:
>
> One major work will be to build the slim_install repository and re-brand the
> Caiman installer.
>

I will take care of this. I am basing it on the latest slim_install
sources from the repo.

-Shiv


From shivakumar.gn at gmail.com  Wed Jun 18 06:53:47 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Wed, 18 Jun 2008 19:23:47 +0530
Subject: [belenix-dev] wine 1.0 released
Message-ID: <319ee2b10806180653v7da0e8b6g27407005f2d1e083@mail.gmail.com>

Wine 1.0 was released yesterday. This is the first stable release of
Wine after 15 years of development and beta testing !
See: http://www.winehq.org

On a side note, currently BeleniX svn repository has 1.0 RC2 (thanks
to Albert Lee's contribution to sfe repo).

regards
Shiv


From sriramnrn at gmail.com  Wed Jun 18 10:25:09 2008
From: sriramnrn at gmail.com (Sriram Narayanan)
Date: Wed, 18 Jun 2008 22:55:09 +0530
Subject: [belenix-dev] Fwd: [belenix-notify] SF.net SVN: belenix: [112]
	trunk/spec_files/SFEwine.spec
In-Reply-To: <E1K90je-0003Ta-EJ@sc8-pr-svn2.sourceforge.net>
References: <E1K90je-0003Ta-EJ@sc8-pr-svn2.sourceforge.net>
Message-ID: <49977f270806181025h21959742rb3bed0554eb5ce49@mail.gmail.com>

I'm pleased to report the Wine 1.0 builds just fine on Belenix (when
you use the spec file below).

I have been able to run Lotus Notes on it :)

Now, it's time to test Firefox and VPNC next !

-- Sriram


---------- Forwarded message ----------
From: belenix-notify <belenix-notify at lists.sourceforge.net>
Date: Wed, Jun 18, 2008 at 10:12 PM
Subject: [belenix-notify] SF.net SVN: belenix: [112]
trunk/spec_files/SFEwine.spec
To: belenix-notify at lists.sourceforge.net


Revision: 112
         http://belenix.svn.sourceforge.net/belenix/?rev=112&view=rev
Author:   dynamicproxy
Date:     2008-06-18 09:42:11 -0700 (Wed, 18 Jun 2008)

Log Message:
-----------
Wine 1.0. I ran Notepad so far, have to test everything else of course

Modified Paths:
--------------
   trunk/spec_files/SFEwine.spec

Modified: trunk/spec_files/SFEwine.spec
===================================================================
--- trunk/spec_files/SFEwine.spec       2008-06-14 11:41:05 UTC (rev 111)
+++ trunk/spec_files/SFEwine.spec       2008-06-18 16:42:11 UTC (rev 112)
@@ -10,7 +10,7 @@

 Name:                   SFEwine
 Summary:                Windows Emulator
-Version:                1.0-rc2
+Version:                1.0
 URL:                    http://www.winehq.org/
 Source:                 %{src_url}/%{src_name}-%{version}.tar.bz2
 Patch1:                        wine-01-nameconfict.diff


This was sent by the SourceForge.net collaborative development
platform, the world's largest Open Source development site.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
belenix-notify mailing list
belenix-notify at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/belenix-notify


From moinakg at gmail.com  Wed Jun 18 11:10:56 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Wed, 18 Jun 2008 23:40:56 +0530
Subject: [belenix-dev] Fwd: [belenix-notify] SF.net SVN: belenix: [112]
	trunk/spec_files/SFEwine.spec
In-Reply-To: <49977f270806181025h21959742rb3bed0554eb5ce49@mail.gmail.com>
References: <E1K90je-0003Ta-EJ@sc8-pr-svn2.sourceforge.net>
	<49977f270806181025h21959742rb3bed0554eb5ce49@mail.gmail.com>
Message-ID: <46fe20470806181110v21d17982uf4d8808781bc2f1c@mail.gmail.com>

On Wed, Jun 18, 2008 at 10:55 PM, Sriram Narayanan <sriramnrn at gmail.com> wrote:
> I'm pleased to report the Wine 1.0 builds just fine on Belenix (when
> you use the spec file below).
>
> I have been able to run Lotus Notes on it :)
>
> Now, it's time to test Firefox and VPNC next !

   Great!. BTW just as an idea it might be possible to create a Windows
   Zone using Wine + Branded Zones. Should be an interesting project.

Regards,
Moinak.

>
> -- Sriram
>
>
> ---------- Forwarded message ----------
> From: belenix-notify <belenix-notify at lists.sourceforge.net>
> Date: Wed, Jun 18, 2008 at 10:12 PM
> Subject: [belenix-notify] SF.net SVN: belenix: [112]
> trunk/spec_files/SFEwine.spec
> To: belenix-notify at lists.sourceforge.net
>
>
> Revision: 112
>         http://belenix.svn.sourceforge.net/belenix/?rev=112&view=rev
> Author:   dynamicproxy
> Date:     2008-06-18 09:42:11 -0700 (Wed, 18 Jun 2008)
>
> Log Message:
> -----------
> Wine 1.0. I ran Notepad so far, have to test everything else of course
>
> Modified Paths:
> --------------
>   trunk/spec_files/SFEwine.spec
>
> Modified: trunk/spec_files/SFEwine.spec
> ===================================================================
> --- trunk/spec_files/SFEwine.spec       2008-06-14 11:41:05 UTC (rev 111)
> +++ trunk/spec_files/SFEwine.spec       2008-06-18 16:42:11 UTC (rev 112)
> @@ -10,7 +10,7 @@
>
>  Name:                   SFEwine
>  Summary:                Windows Emulator
> -Version:                1.0-rc2
> +Version:                1.0
>  URL:                    http://www.winehq.org/
>  Source:                 %{src_url}/%{src_name}-%{version}.tar.bz2
>  Patch1:                        wine-01-nameconfict.diff
>
>
> This was sent by the SourceForge.net collaborative development
> platform, the world's largest Open Source development site.
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> belenix-notify mailing list
> belenix-notify at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/belenix-notify
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>


From moinakg at gmail.com  Wed Jun 18 20:08:24 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Thu, 19 Jun 2008 08:38:24 +0530
Subject: [belenix-dev] Testing Firefox 3
Message-ID: <46fe20470806182008o43c4c510p8f04586eb421efca@mail.gmail.com>

Hi Folks,

   I have built FF3 on BeleniX and uploaded to the new BeleniX machine.
It will help if folks can test this new package on BeleniX 0.7. You can
get the package from:

http://www.belenix.net/binfiles/SUNWfirefox.tar.gz

The process to install this is as follows:

1) Download and uncompress the package:
   gunzip -c SUNWfirefox.tar.gz | tar xf -

2) Remove existing Firefox packages:
   pkgrm SUNWfirefox SUNWfirefox-root

3) Add new package:
   pkgadd -d . SUNWfirefox

Regards,
Moinak.


From maybird1776 at yahoo.com  Thu Jun 19 06:28:04 2008
From: maybird1776 at yahoo.com (ken mays)
Date: Thu, 19 Jun 2008 06:28:04 -0700 (PDT)
Subject: [belenix-dev] Testing Nvidia driver 177.13
Message-ID: <662569.68238.qm@web34207.mail.mud.yahoo.com>

Ref: http://www.nvidia.com/object/solaris_display_177.13.html

- Added support for the following new GPUs: 
GeForce GTX 260 
GeForce GTX 280 

This driver supports all of the currently sold Nvidia Geforce FX graphics
and works very well on the curent Sun Ultra workstations. Highly preferred for the next Belenix 0.7.1 release!!

~ Ken Mays



      


From sriramnrn at gmail.com  Thu Jun 26 10:21:38 2008
From: sriramnrn at gmail.com (Sriram Narayanan)
Date: Thu, 26 Jun 2008 22:51:38 +0530
Subject: [belenix-dev] Errors in the latest Firefox SFE checkins
Message-ID: <49977f270806261021n2dcdac2t200a1de52223e812@mail.gmail.com>

I'm attaching the log files.

-- Ram
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SUNWfirefox3.log
Type: application/octet-stream
Size: 383468 bytes
Desc: not available
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080626/480686fd/attachment.obj>

From sriramnrn at gmail.com  Thu Jun 26 10:30:33 2008
From: sriramnrn at gmail.com (Sriram Narayanan)
Date: Thu, 26 Jun 2008 23:00:33 +0530
Subject: [belenix-dev] Fwd: Errors in the latest Firefox SFE checkins
In-Reply-To: <49977f270806261021n2dcdac2t200a1de52223e812@mail.gmail.com>
References: <49977f270806261021n2dcdac2t200a1de52223e812@mail.gmail.com>
Message-ID: <49977f270806261030l2a3fb5bey53af82083b420b7c@mail.gmail.com>

I'm on Belenix 0.7


---------- Forwarded message ----------
From: Sriram Narayanan <sriramnrn at gmail.com>
Date: Thu, Jun 26, 2008 at 10:51 PM
Subject: Errors in the latest Firefox SFE checkins
To: Belenix Developers <belenix-dev at opensolaris.org>


I'm attaching the log files.

-- Ram
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SUNWfirefox3.log
Type: application/octet-stream
Size: 383468 bytes
Desc: not available
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080626/de75099f/attachment.obj>

From moinakg at gmail.com  Thu Jun 26 11:01:34 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Thu, 26 Jun 2008 23:31:34 +0530
Subject: [belenix-dev] Errors in the latest Firefox SFE checkins
In-Reply-To: <49977f270806261021n2dcdac2t200a1de52223e812@mail.gmail.com>
References: <49977f270806261021n2dcdac2t200a1de52223e812@mail.gmail.com>
Message-ID: <46fe20470806261101r2e1152d2n16b6e487b282b142@mail.gmail.com>

Ouch looks like an assert failure inside of SUN Studio! Are you trying with SUN
Studio 11 or 12 ?

I was able to build it in my BeleniX chroot using Sun Studio 12.

Regards,
Moinak.

On Thu, Jun 26, 2008 at 10:51 PM, Sriram Narayanan <sriramnrn at gmail.com> wrote:
> I'm attaching the log files.
>
> -- Ram
>
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
>


From moinakg at gmail.com  Thu Jun 26 12:03:31 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Fri, 27 Jun 2008 00:33:31 +0530
Subject: [belenix-dev] New binutils and Gcc4 packages are built
Message-ID: <46fe20470806261203g2820d0ady103c60e831a3f442@mail.gmail.com>

Hiya Folks,

   Thanks to Michael Kosarev there is a beefy BeleniX build machine available
installed with 0.7 as of now. The plan for near future is to use that
as a common
build server for the core contributors and provision zones for developers to be
able to experiment and share workspaces easily.  I will provide further updates
as and when things get setup and a process is worked out.

For testing I setup a new chroot environment on that box by zfs-cloning the root
pool and pulled a copy of the BeleniX SVN repository. I then managed to get
SFEbinutils and SFEgcc (Gcc4) built on 0.7. I had to install Studio 11 as well.

These packages are available from:
http://www.belenix.net/binfiles/extra_packages/

SFEbinutils.tar.bz2, SFEbinutils-devel.tar.bz2, SFEgccruntime.tar.bz2,
SFEgcc.tar.bz2

You will have  to download and unzip and untar these files and pkgadd them. If
you have untarred in the current directory then the following command
will do the
trick:

pkgadd -d . SFEbinutils SFEbinutils-devel SFEgccruntime SFEgcc

Gcc4 is impt in order to successfully build KDE4.

Regards,
Moinak.


From shivakumar.gn at gmail.com  Sun Jun 29 03:17:30 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Sun, 29 Jun 2008 15:47:30 +0530
Subject: [belenix-dev] New binutils and Gcc4 packages are built
In-Reply-To: <46fe20470806261203g2820d0ady103c60e831a3f442@mail.gmail.com>
References: <46fe20470806261203g2820d0ady103c60e831a3f442@mail.gmail.com>
Message-ID: <319ee2b10806290317h5601239i65f4c71a1b614378@mail.gmail.com>

On Fri, Jun 27, 2008 at 12:33 AM, Moinak Ghosh <moinakg at gmail.com> wrote:
> Hiya Folks,
>
>   Thanks to Michael Kosarev there is a beefy BeleniX build machine available
> installed with 0.7 as of now. The plan for near future is to use that
> as a common
> build server for the core contributors and provision zones for developers to be
> able to experiment and share workspaces easily.  I will provide further updates
> as and when things get setup and a process is worked out.
>

This is awesome....
Between genunix and the new machine the infrastructure requirements
for content/hosting and builds become complete....

-Shiv


From manishchaks at gmail.com  Mon Jun 30 04:39:40 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Mon, 30 Jun 2008 17:09:40 +0530
Subject: [belenix-dev] New binutils and Gcc4 packages are built
In-Reply-To: <46fe20470806261203g2820d0ady103c60e831a3f442@mail.gmail.com>
References: <46fe20470806261203g2820d0ady103c60e831a3f442@mail.gmail.com>
Message-ID: <D1C50A32-27CF-4C2D-8CC2-39F80FEAB286@gmail.com>

This is good news.
I must then recompile stuff with gcc4 for me kde4 stuff.


On 27-Jun-08, at 12:33 AM, Moinak Ghosh wrote:

> Hiya Folks,
>
>   Thanks to Michael Kosarev there is a beefy BeleniX build machine  
> available
> installed with 0.7 as of now. The plan for near future is to use that
> as a common
> build server for the core contributors and provision zones for  
> developers to be
> able to experiment and share workspaces easily.  I will provide  
> further updates
> as and when things get setup and a process is worked out.
>
> For testing I setup a new chroot environment on that box by zfs- 
> cloning the root
> pool and pulled a copy of the BeleniX SVN repository. I then managed  
> to get
> SFEbinutils and SFEgcc (Gcc4) built on 0.7. I had to install Studio  
> 11 as well.
>
> These packages are available from:
> http://www.belenix.net/binfiles/extra_packages/
>
> SFEbinutils.tar.bz2, SFEbinutils-devel.tar.bz2, SFEgccruntime.tar.bz2,
> SFEgcc.tar.bz2
>
> You will have  to download and unzip and untar these files and  
> pkgadd them. If
> you have untarred in the current directory then the following command
> will do the
> trick:
>
> pkgadd -d . SFEbinutils SFEbinutils-devel SFEgccruntime SFEgcc
>
> Gcc4 is impt in order to successfully build KDE4.
>
> Regards,
> Moinak.
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev



From moinakg at gmail.com  Mon Jun 30 04:45:03 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Mon, 30 Jun 2008 17:15:03 +0530
Subject: [belenix-dev] New binutils and Gcc4 packages are built
In-Reply-To: <D1C50A32-27CF-4C2D-8CC2-39F80FEAB286@gmail.com>
References: <46fe20470806261203g2820d0ady103c60e831a3f442@mail.gmail.com>
	<D1C50A32-27CF-4C2D-8CC2-39F80FEAB286@gmail.com>
Message-ID: <46fe20470806300445s520f007dvf17afcd4eb296d78@mail.gmail.com>

On Mon, Jun 30, 2008 at 5:09 PM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
> This is good news.
> I must then recompile stuff with gcc4 for me kde4 stuff.

   That is the idea :)

Regards,
Moinak.

>
>
> On 27-Jun-08, at 12:33 AM, Moinak Ghosh wrote:
>
>> Hiya Folks,
>>
>>   Thanks to Michael Kosarev there is a beefy BeleniX build machine
>> available
>> installed with 0.7 as of now. The plan for near future is to use that
>> as a common
>> build server for the core contributors and provision zones for
>> developers to be
>> able to experiment and share workspaces easily.  I will provide
>> further updates
>> as and when things get setup and a process is worked out.
>>
>> For testing I setup a new chroot environment on that box by zfs-
>> cloning the root
>> pool and pulled a copy of the BeleniX SVN repository. I then managed
>> to get
>> SFEbinutils and SFEgcc (Gcc4) built on 0.7. I had to install Studio
>> 11 as well.
>>
>> These packages are available from:
>> http://www.belenix.net/binfiles/extra_packages/
>>
>> SFEbinutils.tar.bz2, SFEbinutils-devel.tar.bz2, SFEgccruntime.tar.bz2,
>> SFEgcc.tar.bz2
>>
>> You will have  to download and unzip and untar these files and
>> pkgadd them. If
>> you have untarred in the current directory then the following command
>> will do the
>> trick:
>>
>> pkgadd -d . SFEbinutils SFEbinutils-devel SFEgccruntime SFEgcc
>>
>> Gcc4 is impt in order to successfully build KDE4.
>>
>> Regards,
>> Moinak.
>> _______________________________________________
>> belenix-dev mailing list
>> belenix-dev at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>


From moinakg at gmail.com  Mon Jun 30 20:51:04 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Tue, 1 Jul 2008 09:21:04 +0530
Subject: [belenix-dev] A testing ISO available
Message-ID: <46fe20470806302051x6cfec78esefd15950bd66fe37@mail.gmail.com>

Hi Folks,

   A testing ISO of the upcoming next release is available for
download from here:

http://www.belenix.net/binfiles/belenix.0.7.1_test1.iso
http://www.belenix.net/binfiles/belenix.0.7.1_test1.iso.md5sum

Note that this is a work in progress and obviously does not yet fix
all the Bugs or RFEs. Some of the changes include:

   - Based on ON Build 90
   - Updated Fully Open X bits.
   - KDE updated to 3.5.9 and some upstream patches removed
   - Firefox3
   - Sham's RAM based Boot integrated. In Grub screen select
     more options to see that boot option.
   - Caiman Installer updated to current version. Install not yet
     tested.
   - Added PowerTOP
   - Added XVM PV drivers to support booting inside domU
   - Qt 3.x is now built in both 32Bit and 64Bit versions.
   - Gtk-Qt3 is fixed to build with proper Solaris build flags so the
     nagging warning about /proc/.../cmdline does not appear.
   - Updated man pages to new release.
   - OpenMotif updated to fix some brokenness

Regards,
Moinak.