On Mon, Jun 15, 2020 at 5:45 AM Bruce Ashfield <[email protected]> wrote: > > On Mon, Jun 15, 2020 at 5:11 AM Christopher Clark > <[email protected]> wrote: > > > > On Fri, Jun 5, 2020 at 5:58 PM Corey Minyard <[email protected]> wrote: > > > > > > On Fri, Jun 05, 2020 at 07:53:53PM -0400, Bruce Ashfield wrote: > > > > On Fri, Jun 5, 2020 at 5:16 PM Corey Minyard <[email protected]> > > > > wrote:
> > > > > Ok. The layer has the following basic pieces: > > > > > 3 The addition of xen-tools. This seems somewhat controversial from a > > > > > naming point of view, at least. But all the major distros seem to > > > > > have it, and it does make things easier. It brings along a boatload > > > > > of perl recipes. > > > > > > Christopher might have a better idea about #3, but if the > > > > functionality is useful, I'm all for having it close to the other Xen > > > > components. > > > > I think if there's users wanting it, it's worth considering and I > > agree with Bruce that meta-virtualization will be the right layer. I > > think the name chosen by the software authors is somewhat unfortunate, > > so getting sign off from the Xen Community Manager about whether the > > use of the trademark is OK would be sensible for Yocto's license > > compliance; but from my (basic) understanding of the policy, it should > > be fine. > > > > I think it's appropriate to retain the 'xen-tools' package name in > > Yocto for the tools provided by the Xen Project source code, since > > those are core Xen system components, with wider Xen community > > involvement in their development and use than these perl system > > management scripts. I don't mind the recipe/package for these perl > > tools being called xen-tools-extra, but getting thumbs up from the Xen > > Community Manager would be best. > > Sounds like a good approach. Following up on this: I did make contact seeking guidance on this, but have not yet received an answer, so I'm going to make a request: Corey: Please can this software be submitted for inclusion to meta-virtualization, using this recipe and package name: perl-xen-management-scripts This will make it obvious that the software is clearly separate from the main Xen hypervisor tools that are maintained within the Xen Project, and the name transparently describes what it provides. thanks, Christopher
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#5460): https://lists.yoctoproject.org/g/meta-virtualization/message/5460 Mute This Topic: https://lists.yoctoproject.org/mt/74701134/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
