Op 5 okt. 2011 om 09:14 heeft Philip Balister <[email protected]> het volgende geschreven:
> On 10/04/2011 06:43 PM, Mark Hatle wrote: >> On 10/4/11 3:32 PM, Saul Wold wrote: >>> On 10/04/2011 01:27 PM, Philip Balister wrote: >>>> On 10/04/2011 04:08 PM, Saul Wold wrote: >>>>> On 10/04/2011 12:58 PM, Philip Balister wrote: >>>>>> I'm about to start bringing some images I use from OE to OE-core. The >>>>>> first issue I saw is there is no task-proper-tools in oe-core (where >>>>>> oe-core means the set of layers created by the Angstrom setup scripts). >>>>>> >>>>> Philip, >>>>> >>>>> Have you looked at task-core-basic, it is supposed to be more of a >>>>> desktop like set of tools, the idea being it's heavier weight than core, >>>>> will move to supporting the non-graphical part of LSB. >>>>> >>>>> Another caveat for task-core-basic is that it's the largetest non-gplv3 >>>>> task that is used by core-image-basic. >>>>> >>>>> Does this task approach what you are looking for? >>>> >>>> It looks like a start, but I notice it brings in rpm. I'm not sure if I >>>> want that. I would have thought that the package manager would be a >>>> distro decision. >>>> >>> That's a bug that I would certainly take a patch for, unless rpm is >>> required as part of LSB, that will need to be verified. >> >> The ability to install RPM packages is required by the LSB. The LSB does not >> require RPM however. (yes I know, odd requirement, but with things like >> alien >> it's doable on debian systems.) >> >> But yes, RPM is included to satisfy that requirement. > > This is beginning to look like a trickier problem than I would like. Between > oe-core and meta-angstrom, there are a number of tasks/images to start from, > but they each have something I don't like: > > 1) I do not want rpm in the image. This would confuse my customer base. > 2) I am tired of dropbear, I want openssh only. fwiw 0.53 fixed most of my problems (e.g x11 forwarding), does it fix your issues as well? > 3) I need the full versions of tools, not the busybox ones. > 4) I am not limited to gpv2 software. > > Richard, it looks to me like we should add an item for the next Yocto > development cycle to review how images are built and try to make the base > stuff in oe-core more usable by everyone. We need to define what choices are > made by distros. For example opkg, rpm, no package management in image. > Images may want dropbear or openssh. > > Short term, I think I'll copy the tasks/images into my bsp and get some stuff > together for testing. I'd like a better long term solution though. > > Philip > > _______________________________________________ > Openembedded-core mailing list > [email protected] > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
