The buildtime will naturally increase as improvements are made etc. One
can expect this sort of thing to happen. The only solution that I can
think of to that (if possible would be applicable to the current targets
now but I am not sure how feasable this is) is to allow exclusion of
unwanted or unnecessary modules.
About postponing the decision; I am not in any rush to see it implemented,
not sure about others. A poll (as Andrew Green originally suggested) is
not an idea I would dismiss though. At least it would give some insight as
to who would want to be seeing this implemented or not.
On Wed, 30 Mar 2011 18:47:12 +1100, Olaf Siejka <caemyr at gmail.com> wrote:
> - buildtime increase? It wont be much, but still, every build target
> means
> some time spent
>> Are we ready for such decision? I think it could be postponed to next
> month.
>> 2011/3/30 Adam <geekdundee at gmail.com>
>>> Looks like an interesting project. Another advantage I see is that we
>> can
>> potentially rid ourselves of the text-based setup and have a GUI based
>> setup and thus make the install potentially quicker.
>>>> I would definitely put a vote in for this one.
>>>> As for the larger ISO - the Linux ISOs I notice tend to be much larger
>> anyway at the moment. I would be more worried if it exceeds 180MB or
>> so. :)
>>>> On Wed, 30 Mar 2011 16:16:11 +1100, Andrew Green <greeniekin at gmail.com>
>> wrote:
>>>>>> Could a vote on merging the livecd and bootcd(no cab file) be put up
>>> in the meeting?
>>> The mailing list has not really been an indicator of what everyone
>>> wants.
>>> I suppose a ram disk could be used and install from a cab. Though I
>>> know nothing about how this would work and if this could be
>>> implemented in the 2 to 3 weeks that could be spent on merging the
>>> discs.
>>>>>> Advantages
>>> -Only build and maintain one cd.
>>> -Saves space on server(not having to build and save 2 discs)
>>> -No confusion about what cd someone installed from.
>>> -Simple to implement as opposed to a ram disk. to install everything
>>> to from a cab.
>>>>>> Disadvantages
>>> -To download an iso to just install will be larger(A compressed
>>> version could counter this. Though it's not ideal)
>>>>>>>>>>>>>>>>>> On Tue, Mar 29, 2011 at 7:34 PM, victor martinez
>>> <vicmarcal at hotmail.com>
>>> wrote:
>>>>>>> Gabriel, nice to see you around!!
>>>> :)
>>>>>>>> ________________________________
>>>> From: gabrielilardi at hotmail.it>>>> To: ros-dev at reactos.org>>>> Date: Tue, 29 Mar 2011 08:45:53 +0200
>>>> Subject: Re: [ros-dev] Meeting on Thursday
>>>>>>>> Hi Colin,
>>>> Please add me to the list, I'm quite busy with rl but I still want to
>>>> be
>>>> in
>>>> :)
>>>>>>>> Gabriel.
>>>>>>>> Date: Tue, 29 Mar 2011 00:32:20 +0200
>>>>> From: colin at reactos.org>>>>> To: ros-dev at reactos.org>>>>> Subject: [ros-dev] Meeting on Thursday
>>>>>>>>>> Hi folks,
>>>>>>>>>> As proposed in our urgent meeting in February, we are going to have
>>>>> regular meetings at 20:00 UTC on the last Thursday of every month.
>>>>> Next
>>>>> Thursday will be the first time to hold such a meeting.
>>>>>>>>>> While I was preparing the technical side (we're going to have a
>>>>> dedicated IRC server with voting capabilities this time), Amine and
>>>>> Victor have come up with a meeting agenda. We have agreed on the
>>>>> following points in this order:
>>>>>>>>>> - ReactOS member definition. Proposal is not to establish a fixed
>>>>> definition, but decide upon always keeping a list of people and just
>>>>> giving hints on how you can get on this list
>>>>> - Current ReactOS work. Developers saying what they are working on
>>>>> - Status of our GSoC participation, in particular students and
>>>>> mentors
>>>>> - Upcoming LinuxTag event on 11th to 14th May
>>>>> - Sum up of previous events, ideas for next ones
>>>>> - Website revamp. Current status, who is working, who is willing to
>>>>> help
>>>>>>>>>> You see that the list is more about inquiring and getting information
>>>>> than doing vital decisions this time. The agenda is also prioritized
>>>>> so
>>>>> that people may leave if they don't want to participate in website
>>>>> discussions for example.
>>>>> If nobody else volunteers, Amine would be in the minute taker
>>>>> position
>>>>> again and I would take the meeting leader role.
>>>>>>>>>> My current list of ReactOS members is as follows. Only these people
>>>>> will
>>>>> be able to participate in the discussions and votings, so please
>>>>> tell me
>>>>> if I have forgotten anybody or if you want to be added to this list:
>>>>>>>>>> - Giannis Adamopoulos (smiley1_)
>>>>> - Johannes Anderwald (janderwald)
>>>>> - Javier Agustìn Fernàndez Arroyo (elhoir)
>>>>> - Maciej Bialas (niski)
>>>>> - Aleksey Bragin (abragin)
>>>>> - Colin Finck (Colin_Finck)
>>>>> - Danny Götte (dangerground)
>>>>> - Cameron Gutman (aicom)
>>>>> - Ziliang Guo (ZWabbit)
>>>>> - Rafal Harabien (rafalh)
>>>>> - Kamil Hornicek (Pigglesworth)
>>>>> - Amine Khaldi (AmineKhaldi)
>>>>> - Timo Kreuzer (tkreuzer)
>>>>> - Matthias Kupfer (Collibri)
>>>>> - Michael Martin (mjmartin)
>>>>> - Victor Martinez (vicmarcal)
>>>>> - Roel Messiant (Mephisto)
>>>>> - Andrew Munger (WaxDragon)
>>>>> - Ged Murphy (GedMurphy)
>>>>> - Sylvain Petreolle (Usurp)
>>>>> - Hervé Poussineau (hpoussin)
>>>>> - Daniel Reimer (dreimer)
>>>>> - Pierre Schweitzer (HeisSpiter)
>>>>> - Samuel Serapion (encoded)
>>>>> - Olaf Siejka (Caemyr)
>>>>> - James Tabor (jimtabor)
>>>>> - Art Yerkes (arty)
>>>>>>>>>> Everybody may join the meeting channel as a non-participating
>>>>> observer
>>>>> though. I'll hand you all connection details when we're ready.
>>>>>>>>>> With best regards,
>>>>>>>>>> Colin
>>>>>>>>>> _______________________________________________
>>>>> Ros-dev mailing list
>>>>>Ros-dev at reactos.org>>>>>http://www.reactos.org/mailman/listinfo/ros-dev>>>>>>>>>>>>> _______________________________________________ Ros-dev mailing list
>>>>Ros-dev at reactos.orghttp://www.reactos.org/mailman/listinfo/ros-dev>>>> _______________________________________________
>>>> Ros-dev mailing list
>>>>Ros-dev at reactos.org>>>>http://www.reactos.org/mailman/listinfo/ros-dev>>>>>>>>>>> _______________________________________________
>>> Ros-dev mailing list
>>>Ros-dev at reactos.org>>>http://www.reactos.org/mailman/listinfo/ros-dev>>>>>>>>> --
>> Using Opera's revolutionary email client: http://www.opera.com/mail/>>>>>> _______________________________________________
>> Ros-dev mailing list
>>Ros-dev at reactos.org>>http://www.reactos.org/mailman/listinfo/ros-dev>>
--
Using Opera's revolutionary email client: http://www.opera.com/mail/