Rusty, I don't understand why will you only invest in MIC2. As you said, MIC2 is easy to using. But MIC2 cannot create the development environment for mobiln 1 or 2.
My suggestion is MIC1 should maintain in the future. MIC1 shouldn't be legacy software. MIC1 and MIC2 are written of python. so It's possible to merge to MIC1 from function of MIC2. But MIC1 have to implement flxible more. I think their handling in the following. + MIC1 -------------------------------+ | Development Environment Kit (DEK) | | Development software and testing | | Create moblin1 images | | | | + MIC2 -----------------------+ | | | Create only moblin2 images | | | | the Subset of MIC1 | | | +-----------------------------+ | +-------------------------------------+ But we are confusing that MIC1 and MIC2 are similar in name ;-) ======================================== Mitsutaka Amano MIRACLE LINUX CORPORATION ======================================== Rusty Lynch wrote: > First let me point out that MIC (1 or 2) is a generic tool that can be > used to create images from any yum or apt package repository. > > MIC1 will live as long as people find it useful, which might be to build > stacks that have nothing to do with moblin. Ideally the merits of mic2 > will be such that it becomes an obvious choice to migrate too > (regardless of if you are pulling from mobin repos or not), but that's > up to the project using mic. > > Our long term plan is to invest in MIC2, both in developing the tool > itself, and in creating kickstart files that create images from the > Moblin v2 package repositories. > > There is no such thing as Moblin v1 package repositories. Keeping MIC1 > or making MIC2 work with OSV repositories is a job for that OSV (or open > project associated with the OSV like UME.) > > I don't have specific road map dates, but moorestown specific features > are landing any day now in MIC2. > > --rusty > > On Tue, 2009-02-03 at 23:01 -0700, Tonny Tzeng wrote: >> Per MIC1 git log, it seems MIC1 will be used to build images for >> Moorestown, so will those supports be merged to MIC2? or we will back >> to MIC1 someday? Would any gentlemen advise the roadmap planning for >> MIC? >> >> Thanks >> Tonny >> >> On Wed, Feb 4, 2009 at 7:18 AM, Mitsutaka Amano >> <[email protected]> wrote: >> As you understand, MIC2 can *only* create Moblin v2 Images. >> Actually, Few Intel developer didn't check and maintain MIC1 >> except Prajwal. >> >> I hope to don't unfinished construction... If we will maintain >> it, we >> should do. If we won't maintain it, you have to tell us a >> definite answer. >> >> Best Regards, >> Mitsutaka Amano >> >> >> Rusty Lynch wrote: >> > Personally, I don't see much point in maintaining the >> ability both mic1 >> > and mic2 to generate Moblin v2 stacks. >> > >> > On Tue, 2009-02-03 at 07:15 -0700, Mitsutaka Amano wrote: >> >> Hi, >> >> >> >> As we know, MIC2 was released. MIC2 can create Moblin v2 >> images. >> >> so I think MIC1 won't need for MIC2. >> >> >> >> Will MIC1 need for Moblin v2 in the future? >> >> >> >> Thanks, >> >> ======================================== >> >> Mitsutaka Amano >> >> MIRACLE LINUX CORPORATION >> >> ======================================== >> >> >> >> >> >> Mitsutaka Amano wrote: >> >>> Hi Tariq and related Intel enginners. >> >>> >> >>> Thank you for your a lot of Information about Moblin v2.0 >> Alpha1. >> >>> >> >>> I'd like to know distribution team's opinion about MIC2 >> and MIC handling >> >>> on moblin.org. >> >>> Will we maintain the MIC1 or will be obsolete it in the >> future? >> >>> >> >>> Regards, >> >> _______________________________________________ >> >> Moblin dev Mailing List >> >> [email protected] >> >> >> >> To manage or unsubscribe from this mailing list visit: >> >> https://lists.moblin.org/mailman/listinfo/dev or your user >> account on http://moblin.org once logged in. >> >> >> >> For more information on the Moblin Developer Mailing lists >> visit: >> >> http://moblin.org/community/mailing-lists >> > >> > >> >> _______________________________________________ >> Moblin dev Mailing List >> [email protected] >> >> To manage or unsubscribe from this mailing list visit: >> https://lists.moblin.org/mailman/listinfo/dev or your user >> account on http://moblin.org once logged in. >> >> For more information on the Moblin Developer Mailing lists >> visit: >> http://moblin.org/community/mailing-lists >> >> > > _______________________________________________ Moblin dev Mailing List [email protected] To manage or unsubscribe from this mailing list visit: https://lists.moblin.org/mailman/listinfo/dev or your user account on http://moblin.org once logged in. For more information on the Moblin Developer Mailing lists visit: http://moblin.org/community/mailing-lists
