Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ttmCc-00GucR-4Q for pgsql-pkg-debian@arkaria.postgresql.org; Sun, 16 Mar 2025 11:30:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1ttmCa-00Cmdb-Ie for pgsql-pkg-debian@arkaria.postgresql.org; Sun, 16 Mar 2025 11:30:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ttmCa-00CmdT-8f for pgsql-pkg-debian@lists.postgresql.org; Sun, 16 Mar 2025 11:30:44 +0000 Received: from mail-yw1-x1136.google.com ([2607:f8b0:4864:20::1136]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1ttmCW-003AWN-1K for pgsql-pkg-debian@postgresql.org; Sun, 16 Mar 2025 11:30:43 +0000 Received: by mail-yw1-x1136.google.com with SMTP id 00721157ae682-6feafc707d3so28767857b3.1 for ; Sun, 16 Mar 2025 04:30:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1742124640; x=1742729440; darn=postgresql.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=6lb8o7F9EA+5InxrW+kJ9HRUByPz/S3l5vB5HxRb8m0=; b=CN8cMpe0P7HbK5fqSPplDGF6qpVnMpY62ZdvnWXbnYJWF3NCMClG2EsFJMz6KovEX1 h4FSlDNFY8LXHm2yRc0zvvl0xKOTS5hahsbwrbS9X8nArN56Wgu2sVmynDLhWxBM72WC 4IEKwLNrIa3HZFyigofYlCS4zay09tIJwpY/XqrYxCvO88BFkhYhrWlnvBzMmByvVSRH +LNY2b2PCpFe4RxUnymIQtOSPTc+aVJaQp/EplRy/dUTE/aeTEl8OQMR5xIkZy4aNKfS mrfrB6M+T7ORIzaCh8vV5Sde+LpFavKFXDjihjRCUxVaV89qgjyw0ZWrkNZe5kfgCcN0 NmbA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1742124640; x=1742729440; 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=6lb8o7F9EA+5InxrW+kJ9HRUByPz/S3l5vB5HxRb8m0=; b=Cn7cM/QeTQSfN0ovyBqjorm9iTdRJnhoRWy+/5ov6M/BR+vyX8d9iQUm3StTStkjcg /sHBWPY6jFVzOaicHfN0jFNWF/ADlDNwkRRf4BGciSe/rZA506R8tFl2zFqdKecf5XDe 50PdTuPwprizi0knyFKWjFIrFrAzqyc5jzaRz47TtdEwY1AmApHdu6yR8KzOfhFBqUxG ZASb2g4fW6fPVPc4vIX1LIX/VUtmp9CeQDKyAfi7he58ie+0jhlm02JpdkdVHZufE3W8 em5sV6/Ci1ybjXRP5p01dj0yaBTH/o+tE2RljWPq+lsMo1NYs6aQXUNMO6ZwtGaZxSOr HPqw== X-Forwarded-Encrypted: i=1; AJvYcCXoKaMOvhpTOZIWP8GVi3tX8/yXsJTyGtwDesdYLXJPEbrJiQ0pZ+Wxfiy0Cw+QYzINulHSfogKf44fWyHLVfZm@postgresql.org X-Gm-Message-State: AOJu0YzMCVbEauZ2txiyLeStF6f9y7G1SwAy1SzRXdtLCOvG2Il8wW6h 1NDImsbm9r6NMjFrROqLVjeLp/GICfgWe7dJm0z6tqgmPYvrwXtq9pSBoTQlxOUY4GTXC8o7hRF UYscK4zccOnCZ0SZEcg496J3YRcw= X-Gm-Gg: ASbGncvHBu387IwCvSPY/WN2OpNIOhLUDBup5oPmhH90eFIit1oKsxo8VQgu3QcQDnn vW9T3qgb0Q6XoA7sgjgOiIrYEHBSt8bYyUgQZrm/+jjzpaqqETHl68xQxX7EQi/oB09oVHz9snR KS49W26jfyHAawolYqEJkpvwcm02E3iR9JqNMMwg== X-Google-Smtp-Source: AGHT+IFjQjIQUcwb3gxUK18h6fpEWXIQAJp7ZalLhzNYD4H+XQJICwTFPwWcvPfPMxcVV5t/w79tAllwKh5YMgn0BlA= X-Received: by 2002:a05:690c:360d:b0:6fb:974e:dac3 with SMTP id 00721157ae682-6ff45ebd0eamr117870417b3.13.1742124639860; Sun, 16 Mar 2025 04:30:39 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Brian Cosgrove Date: Sun, 16 Mar 2025 06:30:29 -0500 X-Gm-Features: AQ5f1JoT-VFC71668rCRcnFTLpdYrA8Ft4WeQvv3o91d3NIW2yGdx9Cu7J3eUGA Message-ID: Subject: Re: Packages for pg_doorman To: Smolkin Grigory Cc: Bradford Boyle , Christoph Berg , pgsql-pkg-debian@postgresql.org Content-Type: multipart/alternative; boundary="0000000000005041b90630740026" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000005041b90630740026 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable For such a new piece of infrastructure is there really a compelling reason to support distributions older than Debian bookworm (released 3 years ago)? Do you have any current use-cases for something older? On Sun, Mar 16, 2025 at 4:17=E2=80=AFAM Smolkin Grigory wrote: > > Can we use cargo vendor? > > https://doc.rust-lang.org/cargo/commands/cargo-vendor.html > >My understanding is that Debian policy >does not permit downloading > >during the build [0]. > > >Would it be acceptable to install the compiler from https://rustup.rs/ > during package building? > >> My understanding is that Debian policy does not permit downloading > during the build [0]. > > Ok, I suppose we have to live with distribution compiler. Though, it may > make some old systems without rust 1.70.0 unsupportable. > > >> According to this post [1] on the debian-rust mailing list, "vendoring > should be avoided unless there is a very good reason not to". > >> The Debian Rust packaging team has a pretty comprehensive guide [2] an= d > it looks like they have tooling to help assist with the packaging process= . > > I think we have a very good reason here - a lot of distributions of > different versions with different libversions. Even making it just to be > "compilable" would require tremendous effort, supporting it will be > unmanageable. > > I see no good reason not to use vendoring in case of "multiple > distribution"-build process. > 1. It's a tarboll artifact, released with main project, under the sam= e > release tag. > 2. It is reproducible and has public hash, so it can be verified. > 3. It allows local build, nothing has to be downloaded. > 4. Consistent binary behavior across multiple distributions. > --=20 Brian Cosgrove --0000000000005041b90630740026 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
For such a new piece of infrastructure is there really a c= ompelling reason to support distributions older than Debian bookworm (relea= sed 3 years ago)? Do you have any current use-cases for something older?
On Sun, Mar 16, 2025 at 4:17=E2=80=AFAM Smolkin Grigory = <smallkeen@gmail.com> wrot= e:
> Can we use cargo vendor?=
> https://doc.= rust-lang.org/cargo/commands/cargo-vendor.html
>My understanding is that Debian policy >does not = permit downloading
>during th= e build [0].

>Would it be acceptable to install the com= piler from https://rustup.= rs/ during package building?
>> My understanding is that Debian policy does not permit downloadin= g
during the build [0].

Ok, I suppose we have to live with distribution compiler. Though, i= t may make some old systems without rust 1.70.0 unsupportable.

>> According to this post [1] on the debian-rust mailing list, &q= uot;vendoring should be avoided unless there is a very good reason not to&q= uot;.
>> The Debian Rust p= ackaging team has a pretty comprehensive guide [2] and it looks like they h= ave tooling to help assist with the packaging process.

I th= ink we have a very good reason here - a lot of distributions of different v= ersions with different libversions. Even making it just to be "compila= ble" would require tremendous effort, supporting it will be unmanageab= le.=C2=A0

I see no good reason not to use vendoring in case= of "multiple distribution"-build process.
=C2=A0 =C2=A0 1. It's a tarboll artifact, released= with main project, under the same release tag.
=C2=A0 =C2=A0 2. It is reproducible and has public hash, so= it can be verified.
=C2=A0 =C2= =A0 3. It allows local build, nothing has to be downloaded.
=C2=A0 =C2=A0 4. Consistent binary behavior a= cross multiple distributions.


--
Brian Cosgrove
--0000000000005041b90630740026--