Hi
> -----Original Message-----
> From: Anas Nashif [mailto:[email protected]]
> Sent: Wednesday, January 19, 2011 8:59 PM
> To: Zhu, Peter J
> Cc: [email protected]
> Subject: Re: [meego-packaging] Please READ: Build System project
> restructuring announcement
>
>
> On 17 Jan 2011, at 05:54, Zhu, Peter J wrote:
>
> > Hi,
> >
> > Thank you. A lot of information.
> >
> >>> What's the benefit for this? A not-good thing is that T:T package would
> have
> >> to rebuild if anything promoted to Trunk so that many unnecessary rebuild
> >> would happen.
> >>>
> >>
> >> Lots of benefits actually:
> >>
> >> 1. All meta data is kept in once central place, Trunk in this case. This
> included
> >> information about devel projects and such
> > Currently all devel information are set against T:T. Do we need do something
> to reset to Trunk?
>
> Yes, we need to move this information from Trunk:Testing to Trunk.
>
> >
> >> 2. It is always possible to see what packages in Trunk:Testing have been
> >> changed
> > From experience in MeeGo:1.1, seem the package is still there even a
> request has been promoted into Trunk. So we still have to figure out queued
> changes with our own way like rdiff. Hope OBS has something upgraded for
> this.
>
> You will need to remove those packages after accepting them in Trunk
>
Aah? What do you mean by remove? Remove physically with "osc rdelete" Manually?
Why not OBS do this? For example with just a _link file for those package and
OBS webUI view would filter out those packages with just _link file.
> >
> >> 3. It is possible to build only changes and their dependencies and apply
> >> Trunk:Testing changes on top of an installation of Trunk, very handy when
> >> testing and manageable for example with 'zypper dup'
> > I don't understand here. Seem We can still do this without project link
> > since
> T:T just has limited changes than Trunk. You mean Trunk:Testing repo has
> limited packages just like Trunk:Testing project hosting limited/changed
> packages?
>
> Trunk:Testing is completely self-contained and has its own packages and
> versions, there is no way to combine packages between Trunk and
> Trunk:Testing without breaking the system. With new approach, for a single or
> a few changes that do not cause a complete bootstrap for example, it will be
> easy to just update a Trunk installation with the changes from Trunk:Testing,
> since they share the same, non-rebuild binary packages. (from localdep
> target).
>
>
Ok, this is a good point.
Could you explain a bit more on localdep? Taking a concrete example, if
libmeegotouch changed, what would be in localdep target?
a) only libmeegotouch
b)libmeegotouch + rebuilt packages with this change like
meegotouch-compositor and others
c)libmeegotouch + rebuilt packages + all other untouched packages
>
> >
> >> 4. Guarantee that we use the same sources + project configuration for both
> >> projects, since they are linked
> >> 5. resetting Trunk:Testing, i.e reverting changes is easier, it only
> >> requires
> >> deletion of local package in Trunk:Testing.
> >
> >> 6. Generating diffs between the 2 projects is easier, because only a known
> >> subset of the packages are physically present in Trunk:Testing, no more
> >> confusion about what has been promoted and what not.
> >>
> > Again, From experience in MeeGo:1.1, seem the package is still there even a
> request has been promoted into Trunk
>
>
> We need to remove them once they are accepted into Trunk, there is no reason
> why they should stay in Trunk:Testing.
>
>
> Anas
>
> >
> > Peter
> >> The rebuild time in some cases is something we need to live with, it is
> >> not as
> >> critical as any other mistakes we might do by running and managing
> completely
> >> independent project, Trunk and Trunk:Testing.
> >>
> >> Anas
> >>
> >>
> >>> Peter.
> >>>
> >>>> - 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)
> >>>> * 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
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging
