All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: wltu@google.com
Cc: Tristan Lelong <tlelong@google.com>,
	Ross Burton <Ross.Burton@arm.com>,
	 "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	Khem Raj <raj.khem@gmail.com>
Subject: Re: [OE-core] [PATCH] openssh: Install internal header/lib files
Date: Tue, 8 Nov 2022 17:27:07 +0100	[thread overview]
Message-ID: <CANNYZj8o_GjiqwADQQp5KM_mnQTi+mw6nVh2E1GWVsfi9o3ZKg@mail.gmail.com> (raw)
In-Reply-To: <CAHwn2XmaTHGGUZXn9bC=SBj51zL6eo6rhWPR4SPP_UN0js9-8g@mail.gmail.com>

The correct way to do this is to discuss the issue with openssh
upstream, and provide a link to any such discussion if it has already
happened. If they don't want to install these things, they have
reasons, and you need to at least try to convince them otherwise.

We generally do not go against upstream choices.

Alex

On Tue, 8 Nov 2022 at 17:23, Willy Tu via lists.openembedded.org
<wltu=google.com@lists.openembedded.org> wrote:
>
> Is there anything else that I need to do to help move this forward?
>
> Willy Tu
>
> On Mon, Oct 31, 2022 at 8:42 AM Willy Tu via lists.openembedded.org <wltu=google.com@lists.openembedded.org> wrote:
>>
>> Friendly ping. Is there any more concern on this?
>>
>> Willy Tu
>>
>>
>> On Mon, Oct 24, 2022 at 10:07 AM Willy Tu via lists.openembedded.org
>> <wltu=google.com@lists.openembedded.org> wrote:
>> >
>> > Testing it out more and it seems like the current change is fine in that regard.
>> >
>> > I was building it against an OpenBMC image which include the change and the header and libssh.a files doesn't show up in the image itself
>> >
>> > ```
>> > ./tmp/work/izumi-openbmc-linux-gnueabi/obmc-phosphor-image
>> > ```
>> > doesn't have those files. I believe that's what we are looking for?
>> >
>> > Willy Tu
>> >
>> > On Mon, Oct 24, 2022 at 9:05 AM Willy Tu via lists.openembedded.org <wltu=google.com@lists.openembedded.org> wrote:
>> >>
>> >> I am testing it out again and it seems like it does install to the target .
>> >>
>> >> ```
>> >> $ find -name libssh.a
>> >> ./tmp/sysroots-components/armv7a/openssh/usr/lib/libssh.a
>> >> ./tmp/work/armv7a-openbmc-linux-gnueabi/openssh/9.0p1-r0/image/usr/lib/libssh.a
>> >> ./tmp/work/armv7a-openbmc-linux-gnueabi/openssh/9.0p1-r0/sysroot-destdir/usr/lib/libssh.a
>> >> ./tmp/work/armv7a-openbmc-linux-gnueabi/openssh/9.0p1-r0/packages-split/openssh-staticdev/usr/lib/libssh.a
>> >> ./tmp/work/armv7a-openbmc-linux-gnueabi/openssh/9.0p1-r0/openssh-9.0p1/libssh.a
>> >> ./tmp/work/armv7a-openbmc-linux-gnueabi/openssh/9.0p1-r0/package/usr/lib/libssh.a
>> >> ./tmp/work/armv7a-openbmc-linux-gnueabi/hiba/1.0+gitAUTOINC+3199239c6a-r0/recipe-sysroot/usr/lib/libssh.a
>> >> ```
>> >> We don't want this, right?
>> >>
>> >> I'll have to try to figure it out and fix it.
>> >>
>> >> Willy Tu
>> >>
>> >> On Mon, Oct 24, 2022 at 7:57 AM Tristan Lelong <tlelong@google.com> wrote:
>> >>>
>> >>>
>> >>>
>> >>> On Fri, Oct 21, 2022 at 6:22 PM Willy Tu <wltu@google.com> wrote:
>> >>>>
>> >>>> Hi Ross,
>> >>>>
>> >>>> Thanks for the feedback.
>> >>>>
>> >>>> Can you point to the right repo to update? Just to make sure that I understand the concern, you are not referring to https://github.com/openembedded/meta-openembedded/pull/597, right? I am making changes to http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-connectivity/openssh/openssh_9.0p1.bb which I thought is part of oe-core.
>> >>>>
>> >>>> @Tristan Lelong is the maintainer for hiba and is okay with the change. Do you have any suggestions on installing it to just the sysroot in openssh while using it from the hiba recipe? I was not able to do that when I tried it.
>> >>>
>> >>>
>> >>> This was indeed discussed previously in another version of the patch, it seemed the best way to expose OpenSSH's internal files was via the devel package (not installed on the target), rather than hook into another package's syroot.
>> >>>
>> >>> The OpenSSH static libraries and header files are currently not made officially available because the API is not considered stable enough, but exporting them in OE for HIBA (gated by a PACKAGECONFIG) in order to support HIBA is fine.
>> >>>
>> >>>>
>> >>>>
>> >>>> Thanks,
>> >>>>
>> >>>> Willy Tu
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> On Fri, Oct 21, 2022 at 7:59 AM Ross Burton <Ross.Burton@arm.com> wrote:
>> >>>>>
>> >>>>> Hi,
>> >>>>>
>> >>>>> oe-core doesn’t accept merge requests on the github mirrors, and you pushed to meta-oe, which is a different repository.
>> >>>>>
>> >>>>> >> + if ${@bb.utils.contains('DISTRO_FEATURES', 'opensshinternals', 'true', 'false', d)}; then
>> >>>>>
>> >>>>> This should be a PACKAGECONFIG, as it’s not a distro-wide setting.
>> >>>>>
>> >>>>> >> + install -d ${D}${includedir}/ssh
>> >>>>> >> + install -d ${D}${includedir}/ssh/openbsd-compat
>> >>>>> >> + install -m0644 ${S}/*.h ${D}${includedir}/ssh
>> >>>>> >> + install -m0644 ${S}/openbsd-compat/*.h ${D}${includedir}/ssh/openbsd-compat
>> >>>>> >> +
>> >>>>> >> + install -d ${D}${libdir}
>> >>>>> >> + install -m0644 ${S}/libssh.a ${D}${libdir}
>> >>>>> >> + install -m0644 ${S}/openbsd-compat/libopenbsd-compat.a ${D}${libdir}
>> >>>>> >> + fi
>> >>>>>
>> >>>>> So you’re installing bits of the SSH source into the *target* packages because one piece of software needs the build tree. This is clearly an unsupported use of openssh, as the hiba build instructions literally say “build openssh, then point hiba’s configure at that build tree”.  If
>> >>>>>
>> >>>>> I suggest a better approach would be to have a bbappend in your layer which adds the files you need to *just the sysroot*, so the target packages are unaltered.
>> >>>>>
>> >>>>> Ross
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Tristan Lelong | SRE | tlelong@google.com |
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>> >
>>
>>
>>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#172975): https://lists.openembedded.org/g/openembedded-core/message/172975
> Mute This Topic: https://lists.openembedded.org/mt/94475279/1686489
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>


  reply	other threads:[~2022-11-08 16:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21 13:17 [PATCH] openssh: Install internal header/lib files Willy Tu
2022-10-21 13:19 ` [OE-core] " Willy Tu
2022-10-21 14:59   ` Ross Burton
2022-10-21 16:22     ` Willy Tu
     [not found]       ` <CABC0sH3LFm48+buev6gFFAAoDT2SLqR-r-rndSjx+eU54H5=1w@mail.gmail.com>
2022-10-24 16:04         ` Willy Tu
     [not found]         ` <17210CE2C7C78501.808@lists.openembedded.org>
2022-10-24 17:07           ` Willy Tu
     [not found]           ` <17211049B04D4148.10479@lists.openembedded.org>
2022-10-31 15:42             ` Willy Tu
     [not found]             ` <172331B40D5EBCA0.9941@lists.openembedded.org>
2022-11-08 16:23               ` Willy Tu
2022-11-08 16:27                 ` Alexander Kanavin [this message]
2022-11-08 17:08                   ` Willy Tu
2022-11-08 17:11                     ` Alexander Kanavin
2022-11-08 17:16                       ` Willy Tu
     [not found]                         ` <CABC0sH0DjvXC4Hw7CxM__spomLbN1ntEsV03-CQ=3OgLLDakLg@mail.gmail.com>
2022-11-08 19:21                           ` Alexander Kanavin
     [not found]                           ` <1725B2503015CF3E.24882@lists.openembedded.org>
2022-11-08 19:25                             ` Alexander Kanavin
2022-11-08 19:30                               ` Willy Tu
2022-11-08 19:37                                 ` Alexander Kanavin
2022-11-08 20:20                                   ` Willy Tu
2022-10-21 16:24 ` Michael Opdenacker
2022-10-24 14:27   ` Willy Tu
     [not found]   ` <1721078C03B5AEB6.808@lists.openembedded.org>
2022-10-24 14:38     ` Willy Tu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CANNYZj8o_GjiqwADQQp5KM_mnQTi+mw6nVh2E1GWVsfi9o3ZKg@mail.gmail.com \
    --to=alex.kanavin@gmail.com \
    --cc=Ross.Burton@arm.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=tlelong@google.com \
    --cc=wltu@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.