From nobody Thu Dec 7 01:31:17 2023 X-Original-To: hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SlxZD6rKYz53L8R for ; Thu, 7 Dec 2023 01:31:32 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SlxZD38jHz4WGg for ; Thu, 7 Dec 2023 01:31:32 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-wm1-x334.google.com with SMTP id 5b1f17b1804b1-40c09dfd82aso6345395e9.0 for ; Wed, 06 Dec 2023 17:31:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1701912690; x=1702517490; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=pPp0CbptEfYyjqOjK0+k6CuFM4AgXUqBgcsD5Z2ySvs=; b=WRTewuQYs/ejQ0rsygeI0S7KOm9lVx81keQe/RsIfMd8mDtIy9T/KFvPQ3Ll3YgJG5 XRtN1l9KpNC4GdCLKklFdIc/uECpTcXuo36aFLUJZgOtniqXxjwQoDtLvLgKHr5HC3hf ruq4p4kpqa8nKDwPFVwPTH5XrYRfy/hpsXH+0FsAt3OWWt310kWnmgE0cp+FJdd7Hp9a EK7bEW+sXbCzIGqEaIhWDq3aR8fvDLHTp7mu2EnTyCmBrUz2/UVxDko9HVdh+k9xQ3Jc 4owacBBTsol1nUGOeO6XkZeCG7FpPgqkKYDQ7RvJLRgZeVDPMx4RRgThMzOq25iOoI8s c9bw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701912690; x=1702517490; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=pPp0CbptEfYyjqOjK0+k6CuFM4AgXUqBgcsD5Z2ySvs=; b=hArnk88CYeWEa+UV4jBi4gOMABa2fMalAVS47xCseWVN3RVreCpomG1GcV9pwORLHA We3CSjDZS9/TV9BJTaDtFNDpYACR5x8wFBkjHvTWuG6Ut8Wpf0O3Pmh0EV/Pgw85gHmJ 9Yqm+sOpTHRz9xuImEdp17mZpTIF4QLjY4UxKBkeYgdZA29m37sN/JJStqAgmxTzbuOd 2ln3ih7jJrAS9bCZHccBA8Da38gBhXdaKwm5McTy8bqHsRqa+9jRXeHwSjcvEYLz2ksJ v5kU5VHfxvfIcnEvwo66FzDsvptA8OlZNwVhzoUvEJpt41ABwZwIKIG4iiq3N/i9NsNe w4hg== X-Gm-Message-State: AOJu0YwL6Lahw/Fn4daQmkISSfvSHAFYTVz2sip0Bxd04/QGUAOhs4El JNDwHNDHnj5igYdE2TvpehthYR/qm3Q3GPNhE+NJ1GkOtzVkj+el X-Google-Smtp-Source: AGHT+IG5ObSZfKpRU4oVwEszA2DzdFwuupdEE9FIx5Omppb1g/JvuNTqwO6Ay8lyKMDS2KEU8KRr1JVM+WbMWcae3Ac= X-Received: by 2002:a1c:7706:0:b0:40b:5e21:dd31 with SMTP id t6-20020a1c7706000000b0040b5e21dd31mr1245504wmi.95.1701912689501; Wed, 06 Dec 2023 17:31:29 -0800 (PST) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: <090b5b29-50bd-470a-905b-b9c2016a5189@www.fastmail.com> <8634fd2e-6c8f-4d37-99e2-56f4febd74d9@app.fastmail.com> In-Reply-To: <8634fd2e-6c8f-4d37-99e2-56f4febd74d9@app.fastmail.com> From: Warner Losh Date: Wed, 6 Dec 2023 18:31:17 -0700 Message-ID: Subject: Re: list of valid ABI combinations To: Dan Langille Cc: "freebsd-hackers@freebsd.org" Content-Type: multipart/alternative; boundary="0000000000004c015f060be16d65" X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4SlxZD38jHz4WGg --0000000000004c015f060be16d65 Content-Type: text/plain; charset="UTF-8" On Wed, Dec 6, 2023, 6:01 PM Dan Langille wrote: > On Thu, Apr 9, 2020, at 11:01 AM, Dan Langille wrote: > > Hello, > > > > I'm looking to add package support to FreshPorts - so you can know if a > > package exists for a given ABI (e.g. FreeBSD:12:amd64). > > > > The goal, write a script which does something like this: > > > > for abi in $ABIS > > do > > fetch -o abi. packagesite.txz > > https://pkg.freebsd.org/$abi/latest/packagesite.txz > > # parse the file, updating the database > > done > > > > Is there a list of current valid ABI combinations. > > > > I see a list at https://pkg.freebsd.org/ - is this manually maintained? > > > > While my goal is to have FreshPorts require minimal intervention, I > > suppose new ABI combinations do not come along frequently and could be > > maintained manually. It does not seem like a huge task. > > > > More details here: https://github.com/FreshPorts/freshports/issues/142 > > I see I have been trying to figure this out for a few years. > > Does anyone have any ideas as to where this might be determined? > It should be just the list of valid MACHINE_ARCH (make targets can give you a variation of this list). If you compute the cross product of that list and the supported branches {12,13,14;15} you will know what you can try. However, you need to know the current package builders. It's a subset of branches and abis, but since it's just the packages this should give you a matrix after you fetch. Warner -- > Dan Langille > dan@langille.org > > --0000000000004c015f060be16d65 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Wed, Dec 6, 2023, 6:01 PM Dan Langille <dan@langille.org> wrote:
On Thu, Apr 9, 2020, at 11:01 AM, Dan Langille wr= ote:
> Hello,
>
> I'm looking to add package support to FreshPorts - so you can know= if a
> package exists for a given ABI (e.g. FreeBSD:12:amd64).
>
> The goal, write a script which does something like this:
>
>=C2=A0 =C2=A0for abi in $ABIS
>=C2=A0 =C2=A0do
>=C2=A0 =C2=A0 =C2=A0fetch -o abi. packagesite.txz
> https://pkg.freebsd.org/$abi/late= st/packagesite.txz
>=C2=A0 =C2=A0 =C2=A0# parse the file, updating the database
>=C2=A0 =C2=A0done
>
> Is there a list of current valid ABI combinations.
>
> I see a list at https://pkg.freebsd.org/ - is this manua= lly maintained?
>
> While my goal is to have FreshPorts require minimal intervention, I > suppose new ABI combinations do not come along frequently and could be=
> maintained manually. It does not seem like a huge task.
>
> More details here: https://github= .com/FreshPorts/freshports/issues/142

I see I have been trying to figure this out for a few years.

Does anyone have any ideas as to where this might be determined?

It should b= e just the list of valid MACHINE_ARCH (make targets can give you a variatio= n of this list). If you compute the cross product of that list and the supp= orted branches {12,13,14;15} you will know what you can try. However, you n= eed to know the current package builders. It's a subset of branches and= abis, but since it's just the packages this should give you a matrix a= fter you fetch.

Warner

--
=C2=A0 Dan Langille
=C2=A0 dan@langille.org

--0000000000004c015f060be16d65--