All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Anthony PERARD <anthony.perard@vates.tech>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
	"Juergen Gross" <jgross@suse.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	"Jan Beulich" <JBeulich@suse.com>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Julien Grall" <julien@xen.org>,
	"Oleksii Kurochko" <oleksii.kurochko@gmail.com>
Subject: Re: [PATCH 20/12] CI: Swap from perl to perl-base in build containers
Date: Mon, 15 Jul 2024 14:02:36 +0100	[thread overview]
Message-ID: <377cd22e-e5f9-4675-9d11-92298dc5ce55@citrix.com> (raw)
In-Reply-To: <ZpUaMwZoKnrh61P0@l14>

On 15/07/2024 1:46 pm, Anthony PERARD wrote:
> On Sat, Jul 13, 2024 at 07:09:52PM +0100, Andrew Cooper wrote:
>> We only need a basic perl environment, not the things that a primarily-perl
>> project would want.
>>
>> Discovered during the Fedora refresh where the difference is ~40M, but it's
>> more modest for OpenSUSE and Ubuntu.
> "perl-base" on Ubuntu is quite different from "perl-base" on OpenSUSE
> Leap. I haven't check Tumbleweed but is probably the same as Leap.

/sigh - because that would have been too easy.

> So, I think these would deserve to be in separated patches.
>
> On Ubuntu, installing "perl" or "perl-base" or none of them makes no
> difference. We install "build-essentials" which pulls "dpkg-dev" which
> pulls "perl", so we don't test properly if "perl-base" is enough or if
> we need more.

Fine - lets leave the Ubuntu's alone.

>
> I tried to find out which Perl module we would need, and I've got this
> list:
>
> - get_maintainer
>     Getopt::Long;
> - add_maintainer
>     Getopt::Long;
>     File::Basename;
>     List::MoreUtils;
>     IO::Handle;
> - stubdom/vtpmmgr:
>     Digest::SHA qw(sha1);
>     Math::BigInt only => 'GMP';
> - kconfig
>     Getopt::Long;
> - ocaml/lib/xc/abi-check
>     Data::Dumper;
> - docs/gen-html-index
>     Getopt::Long;
>     IO::File;
>     File::Basename;
> - docs/xen-headers
>     Getopt::Long;
>     File::Find;
>     IO::File;
> (there's also tools/examples/xeninfo.pl, I dont't if that can still work
> or if we need to purge it)

Ewww.

my %xenhosts = ("192.0.2.10" => {"port" => "9363"}, ...

is enough to demonstrate it's a special purpose script.

That file isn't referenced by the Makefile, nor is anything in the vnc/
dir, so we should purge the lot.

>
> Then I've got whatever module is in "perl-base" pkg.
>
> For Leap's perl-base:
>     getopt:long
>     file:basename
>     io:handle
>     io:file
>     file:find
>     data:dumper
>     digest:sha
> So, add_maintainer.pl and the script in stubdom/vtpmmgr won't work. So
> that's probably fine for Leap.

vtpmmgr isn't built by default, so gets 0 testing in CI.  I don't expect
people to be using add_maintainer inside the containers either.

>
> For Ubuntu 22.04 (not check others, but likely about the same)
> there's more packages:
>     perl-base
>         getopt::long
>         file:basename
>         io:handle
>         io:file
>     perl-modules-5.34
>         file:find
>         math:bigint
>     libperl5.34
>         data:dumper
>         digest:sha
>     liblist-moreutils-perl
>         list:MoreUtils
>     librpc-xml-perl
>         rpc:xml
> ("perl" pkg pulls "perl-modules-5.34" and "libperl5.34")
>
> So with just "perl-base", the ocaml's abi-check wouldn't work, as well
> as the docs's script (probably ok for "docs" if we don't use containers
> to build them).

Hmm yeah - we wouldn't want to break that.

>  Also add_maintainer and stubdom/vtpmmgr like for Leap.
>
>
> So I would suggest to not touch the Ubuntu containers, make the change
> to the OpenSUSE one and maybe add the limitation to the commit message.

Ok - I'll do this.

~Andrew


  reply	other threads:[~2024-07-15 13:02 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11 11:15 [PATCH for-4.19 v2 00/12] CI: part 3 (slimline, and PPC/RISCV fixes) Andrew Cooper
2024-07-11 11:15 ` [PATCH 01/12] CI: Fix CONTAINER_UID0=1 scripts/containerize Andrew Cooper
2024-07-11 12:54   ` Anthony PERARD
2024-07-11 11:15 ` [PATCH 02/12] CI: Remove useless/misleading randconfig jobs Andrew Cooper
2024-07-11 13:09   ` Anthony PERARD
2024-07-11 15:16     ` Andrew Cooper
2024-07-11 15:50       ` Anthony PERARD
2024-07-11 16:03         ` Andrew Cooper
2024-07-11 11:15 ` [PATCH 03/12] CI: Drop Debian Jessie dockerfiles Andrew Cooper
2024-07-11 15:27   ` Anthony PERARD
2024-07-11 11:15 ` [PATCH 04/12] CI: Drop Debian Stretch testing Andrew Cooper
2024-07-11 13:20   ` Anthony PERARD
2024-07-11 11:15 ` [PATCH 05/12] CI: Drop Ubuntu Trusty testing Andrew Cooper
2024-07-11 13:26   ` Anthony PERARD
2024-07-11 11:15 ` [PATCH 06/12] CI: Mark Archlinux/x86 as allowing failures Andrew Cooper
2024-07-11 13:37   ` Anthony PERARD
2024-07-11 15:24     ` Andrew Cooper
2024-07-11 11:15 ` [PATCH 07/12] CI: Introduce a debian:12-ppc64le container Andrew Cooper
2024-07-11 14:41   ` Anthony PERARD
2024-07-11 15:50     ` Andrew Cooper
2024-07-11 11:15 ` [PATCH 08/12] CI: Use debian:12-ppc64le for both build and test Andrew Cooper
2024-07-11 16:22   ` Anthony PERARD
2024-07-11 18:08     ` Andrew Cooper
2024-07-11 11:15 ` [PATCH 09/12] CI: Refresh bullseye-ppc64le as debian:11-ppc64le Andrew Cooper
2024-07-11 16:27   ` Anthony PERARD
2024-07-11 11:15 ` [PATCH 10/12] CI: Introduce debian:11/12-riscv64 containers Andrew Cooper
2024-07-11 16:34   ` Anthony PERARD
2024-07-12 11:39   ` Oleksii
2024-07-12 12:30     ` Andrew Cooper
2024-07-15 13:29       ` Oleksii
2024-07-11 11:15 ` [PATCH 11/12] CI: Swap to debian for riscv64 build and test Andrew Cooper
2024-07-11 16:37   ` Anthony PERARD
2024-07-12 11:40   ` Oleksii
2024-07-11 11:15 ` [PATCH 12/12] CI: Refresh and upgrade the GCC-IBT container Andrew Cooper
2024-07-11 16:42   ` Anthony PERARD
2024-07-11 13:33 ` [PATCH for-4.19 v2 00/12] CI: part 3 (slimline, and PPC/RISCV fixes) Oleksii
2024-07-11 20:23 ` [PATCH 13/12] CI: Refresh OpenSUSE Tumbleweed container Andrew Cooper
2024-07-11 21:04   ` Andrew Cooper
2024-07-11 21:49   ` Olaf Hering
2024-07-11 22:39     ` Andrew Cooper
2024-07-12  6:37       ` Olaf Hering
2024-07-12 11:14   ` [PATCH v2 " Andrew Cooper
2024-07-12 12:33     ` Anthony PERARD
2024-07-12 12:48       ` Andrew Cooper
2024-07-11 21:05 ` [PATCH 14/12] CI: Refresh OpenSUSE Leap container Andrew Cooper
2024-07-12 12:55   ` [PATCH v2 " Andrew Cooper
2024-07-12 13:02     ` Anthony PERARD
2024-07-12 10:48 ` [PATCH 15/12] CI: Refresh Ubuntu Xenial container as 16.04-x86_64 Andrew Cooper
2024-07-12 13:57   ` Anthony PERARD
2024-07-12 14:02   ` Anthony PERARD
2024-07-12 14:05     ` Andrew Cooper
2024-07-12 14:29   ` Anthony PERARD
2024-07-12 15:43     ` Andrew Cooper
2024-07-12 10:48 ` [PATCH 16/12] CI: Refresh Ubuntu Bionic container as 18.04-x86_64 Andrew Cooper
2024-07-12 14:12   ` Anthony PERARD
2024-07-12 14:13     ` Andrew Cooper
2024-07-12 10:48 ` [PATCH 17/12] CI: Refresh Ubuntu Focal container as 20.04-x86_64 Andrew Cooper
2024-07-12 16:29   ` Anthony PERARD
2024-07-12 10:49 ` [PATCH 18/12] CI: Add Ubuntu 22.04 (Jammy) and 24.04 (Noble) testing Andrew Cooper
2024-07-12 16:44   ` Anthony PERARD
2024-07-12 17:01     ` Andrew Cooper
2024-07-13 18:09 ` [PATCH 19/12] docs: Fix install-man$(1)-pages if no manpages are generated Andrew Cooper
2024-07-15 12:05   ` Anthony PERARD
2024-07-13 18:09 ` [PATCH 20/12] CI: Swap from perl to perl-base in build containers Andrew Cooper
2024-07-15 12:46   ` Anthony PERARD
2024-07-15 13:02     ` Andrew Cooper [this message]
2024-07-13 18:10 ` [PATCH 21/12] CI: Refresh and upgrade the Fedora container Andrew Cooper
2024-07-15 13:39   ` Anthony PERARD
2024-07-15 14:39     ` Andrew Cooper
2024-07-15 15:16 ` [PATCH 22/12] tools/examples: Remove more obsolete content Andrew Cooper
2024-07-15 16:53   ` Anthony PERARD
2024-07-15 17:17     ` Andrew Cooper

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=377cd22e-e5f9-4675-9d11-92298dc5ce55@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=anthony.perard@vates.tech \
    --cc=jgross@suse.com \
    --cc=julien@xen.org \
    --cc=oleksii.kurochko@gmail.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /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.