[BangPypers] Weekend Meeting

[Rajeev J Sebastian]

On Fri, Oct 16, 2009 at 11:59 PM, Sriram Narayanan <sriramnrn at gmail.com> wrote:
> On Fri, Oct 16, 2009 at 11:19 PM, Rajeev J Sebastian
> <rajeev.sebastian at gmail.com> wrote:
>> On Fri, Oct 16, 2009 at 10:28 PM, Sriram Narayanan <sriramnrn at gmail.com> wrote:
>>> On Fri, Oct 16, 2009 at 9:58 PM, Rajeev J Sebastian
>>> <rajeev.sebastian at gmail.com> wrote:
>>>> On Fri, Oct 16, 2009 at 9:27 AM, Sriram Narayanan <sriramnrn at gmail.com> wrote:
>>>>> On 10/16/09, Sriram Narayanan <sriramnrn at gmail.com> wrote:
>>>>>>
>>>>>> We can meet at TW this Sunday, no problem.
>>>>>
>>>>> One other thing that we'd discussed the last weekend was how those who
>>>>> are Python savvy can be a part of the Belenix developer community.
>>>>
>>>> Does it use python the way Pardus uses it ? Like the init system,
>>>> service manager, package manager, etc.
>>>
>>> Err.. No. Belenix is a distro that is based on the opensolaris ON
>>
>> Blah blah blah ... yes I know its Solaris etc.
>
> My response was to the larger community, and not to just you :)


That's probably why you started your response with an "Err ... No" right ?


>>
>> Question is, are there are specific Belenix components written in
>> Python, as in Pardus Linux which uses Python extensively ? Or was that
>> a call to developers to create new tools using python ?
>>
>
> There is our stop gap package manager which we wrote since we needed
> to move away from something called pkg-get. We're now considering
> using rpm5 as our package format, with the smart package manager being
> the package manager of choice.
>
> When we'd last met at Thoughtworks last weekend, I'd mentioned that
> the Belenix project would

Would what ?


> After I responded to you previously, I've been reading more about Pardus.
> At present, Belenix uses what Solaris has for service management -
> SMF. Apart from the temporary package manager that I wrote about,
> we've not written anything else using Python for Belenix. We're either
> busy with work, or with porting and testing software packages to
> Belenix.

So basically, you made a call for *developers* for Belenix (as opposed
to *Python developers*). I was trying to clarify that point.

Regards
Rajeev J Sebastian