Re: [DLG-dev] making gnome shell usable

[Sasa O. <ca...@gm...>]

On Fri, Sep 16, 2011 at 4:55 PM, Evan Hisey <eh...@gm...> wrote:
> On Fri, Sep 16, 2011 at 1:28 PM, Sasa Ostrouska <ca...@gm...> wrote:
>> On Fri, Sep 16, 2011 at 10:56 AM, Evan Hisey <eh...@gm...> wrote:
>>> On Fri, Sep 16, 2011 at 2:58 AM, bart van der Hall
>>> <bar...@ho...> wrote:
>>>> Hi All,
>>>>
>>>> as saxa knows, I am back in the production aswell.
>>
>> Welcome back Bart !
>>
>>>>
>>>> I might have some extra news.
>>>> I am working at a service provider, and currently have a vm setup for
>>>> building packages.
>>>> I think we can all share that VM for building packages, and use that as our
>>>> development enviroment.
>>
>> Thats good, why not, but in any case this is not a big deal, building a package
>> fast or slow doesnt change much the thing.
>> The good thing is that we can all have the same install and not need
>> to replicate
>> through the net.
>> The bad is that we will not see install bugs of single packages when
>> installing it
>> many times can point some things out.
>> Another issue can be building against broken base, if one of the dep packages
>> is not build correctly many things will need to change later and be
>> rebuilt due to that
>> broken pack. When we install in many different systems this can also happen,
>> but probably we can catch it up faster.
>> We can try, imo.
>>
>>
> We could try setting something like Tinderbox up to test build an see
> if it breaks so we can roll back things that broke. Having a single
> point to do "release builds" on would ensure everything really does
> work as expected.
>
>
>
> Evan
>
> ------------------------------------------------------------------------------
> BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
> http://p.sf.net/sfu/rim-devcon-copy2
> _______________________________________________
> Dropline-gnome-devel mailing list
> Dro...@li...
> https://lists.sourceforge.net/lists/listinfo/dropline-gnome-devel
>

Evan yes, that could work, but to do that we really need firstly to
develop out the scripts, so
script working is difficult to automate, I don't see much sense in
rebuilding and rebuilding
until we get a full build.

Anyway, I think there is plenty of things we can work out.

Suggest what we could do.

Personally I think that to get a good build at least for the first
time, we need to work out the scripts one by one.
To test the script we need to build it. Thats a fact. After that we
can try to automate the thingy.

Rgds
Saxa

Rgds
Saxa