On 17 Jan 2011, at 03:30, Yin, Yan wrote:
> Hi,
>
> Regards,
> Yin, Yan
>
>
>> -----Original Message-----
>> From: [email protected] [mailto:meego-packaging-
>> [email protected]] On Behalf Of Nashif, Anas
>> Sent: Saturday, January 15, 2011 11:48 PM
>> To: [email protected]
>> Subject: [meego-packaging] Please READ: Build System project
>> restructuring announcement
>>
>> Hi,
>> As a measure of cleanup and to better reflect the MeeGo architecture in
>> the build system, we are planning to redo the project structure.
>> The restructuring would happen in three steps, starting with the least
>> intrusive one:
>>
> According to the MeeGo Architecture Layer View, Application Framework like
> Clutter/MX/MeeGo Touch Framework are not part of Core OS, does this mean
> these packages will be move from Trunk to Trunk:UX?
>
> Another question here, some packages are vertical specific, for example, lirc
> package to support infra-red remote control for TV, joystick support for TV,
> some TV specific media codecs, putting them in Core are against the idea that
> MeeGo Core is a common code base for all verticals and should keep as minimal
> as possible. However, they're not part of either Application Framework or
> User Experience as well, it's weird to see some TV specific media codecs
> package stay in UX rather than Core...
>
> To summarize, what's on earth should Trunk:UX include? Could we have a clear
> Guideline here like Trunk:UX should contain packages including User
> Experience +
> Application Framework + Vertical specific packages? or something else?
>
> I like the idea of renaming Trunk to Trunk:Core, as Trunk is too general and
> not reflect the fact it equals MeeGo Core and not aligned with the repo
> naming
> (we have a repo named Core, but the OBS project is named Trunk), could we pull
> in the renaming as the first step, rather than the last step? This is
> something
> long overdue.
This change is very intrusive and will break many links in the build system, it
is not wise to do it right now.
Anas
>
> Thanks,
> Yan.
>
>> 1) Step 1: Start 2011-01-20
>> - Create Trunk:UX and Trunk:UX:Testing
>> - Move Trunk:{Handset|Netbook|IVI}/* to Trunk:UX
>> - Make Trunk:Testing a link to Trunk
>> - Initial package cleanup of new Trunk:UX project.
>> Result:
>> - Trunk
>> - Trunk:UX
>> - Trunk:non-oss
>> With corresponding *:Testing projects.
>>
>> How will this affect you?
>>
>> * This step will produce one single repository for UX and
>> application on top of Core instead of the many we have right now.
>> * Image configurations will need to be changed and would point to at
>> least 3 repos: core, ux and non-oss (if needed)
> Will you change the *.ks file in gitorious or should Release Engineers do
> that?
>
>> * If you have been developing against one of the Trunk sub-projects
>> (Netbook,Handset, IVI), then you will need to re-branch or relink to
>> the new Trunk:UX project
>>
>> 2) Step Two: Start 2011-01-21 - End 2011-03-23
>> - move non-core packages to Trunk:UX, optionally drop or move non-
>> supported packages from both Trunk and Trunk:UX to Community if needed
>>
>> Many packages will be moving around or even completely removed. Please
>> make sure you cleanup your home projects and delete packages or sub-
>> projects you are no longer working on to avoid broken links.
>>
>>
>> 3) Step 3: Start 2011-03-23 (After 1.2 branch)
>> - Rename
>> Trunk -> Trunk:Core,
>> Trunk:Testing -> Trunk:Core:Testing
>>
>> If you have any questions or feedback, please let us know.
>>
>>
>> Regards,
>> Anas Nashif
>>
>>
>> ---------------------------------------------------------------------
>> Intel Corporation (UK) Limited
>> Registered No. 1134945 (England)
>> Registered Office: Pipers Way, Swindon SN3 1RJ
>> VAT No: 860 2173 47
>>
>> This e-mail and any attachments may contain confidential material for
>> the sole use of the intended recipient(s). Any review or distribution
>> by others is strictly prohibited. If you are not the intended
>> recipient, please contact the sender and delete all copies.
>>
>> _______________________________________________
>> MeeGo-packaging mailing list
>> [email protected]
>> http://lists.meego.com/listinfo/meego-packaging
> _______________________________________________
> MeeGo-packaging mailing list
> [email protected]
> http://lists.meego.com/listinfo/meego-packaging
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging
