From nobody Mon Apr 15 17:01:41 2024 X-Original-To: freebsd-ports@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 4VJD3c2Mz5z5GxyR for ; Mon, 15 Apr 2024 17:01:48 +0000 (UTC) (envelope-from portmaster@bsdforge.com) Received: from udns.ultimatedns.net (udns.ultimatedns.net [24.113.41.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "ultimatedns.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VJD3c0xhSz454r; Mon, 15 Apr 2024 17:01:48 +0000 (UTC) (envelope-from portmaster@bsdforge.com) Authentication-Results: mx1.freebsd.org; none Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.16.1/8.16.1) with ESMTP id 43FH1fbG082564; Mon, 15 Apr 2024 10:01:47 -0700 (PDT) (envelope-from portmaster@bsdforge.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ultimatedns.net; s=mx99; t=1713200507; x=1713201107; r=y; bh=4gh9R5415Bh3pCJehP+Dy7VA7rsLq99M3mud8c3euAw=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=nPNVJhpHpnz9Oc6jzAibsEpnbjUSfaJmG7n45N4ckCW9T4TyYAf75fsyCLyccrDm7 WHICltsC5juc+IM/jxsEbuTJzy6PUcYxkExbEEptsZ4lUGIVOzeP8pf1ZQzgiKv6fI 4lmluuak6UlHc5XMyvEiKCcGmHg5hFbCvt8YkF3KTZkHOaepimwxi/KR4caKWQ0dLU jT9K2+pa7uCGIH2HKAjDfVTQrwto4LEZPpiCbWegnbBQGBbqzxLt7683FzqbFPT1U6 D6H7ZSRDPfTirChhaJ9cGEapLGmEY4FRjsEd3ZnuwNIewYM3pXgEm0QcbdV2t3OTLO 7UxaqEJnHblLA== List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-ports@freebsd.org Sender: owner-freebsd-ports@FreeBSD.org MIME-Version: 1.0 Date: Mon, 15 Apr 2024 10:01:41 -0700 From: Chris To: Dimitry Andric Cc: Moin Rahman , FreeBSD Mailing List Subject: Re: holding rust at a particular version In-Reply-To: <559DA6D5-D6F1-4B47-99EA-DC0C0B37417F@FreeBSD.org> References: <20f77d23043622d68d6421bfdc9a1cc7@bsdforge.com> <559DA6D5-D6F1-4B47-99EA-DC0C0B37417F@FreeBSD.org> User-Agent: UDNSMS/17.0 Message-ID: <74510e9480697b29c1b34df3bcf3891f@bsdforge.com> X-Sender: portmaster@bsdforge.com Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: ---- 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:11404, ipnet:24.113.0.0/16, country:US] X-Rspamd-Queue-Id: 4VJD3c0xhSz454r On 2024-04-15 09:58, Dimitry Andric wrote: > On 15 Apr 2024, at 18:48, Chris wrote: >> >> On 2024-04-15 09:31, Moin Rahman wrote: >>>> On Apr 15, 2024, at 6:27 PM, Chris wrote: >>>> On 2024-04-15 06:33, void wrote: >>>>> Is it possible, either within poudriere or using traditional ports, >>>>> to not have ports building fetching latest rust? >>>>> rust 1.76 is already installed. 1.77 is in the ports tree. >>>>> 1.76 is the latest for -current on arm64 on the pkg builders. >>>>> if I go into the ports tree and build something needing rust, >>>>> it'll build 1.77 rust locally instead of using the already-installed >>>>> 1.76. >>>>> which would tie the machine up for hours if not days if allowed to >>>>> proceed. >>>>> Can this be avoided? >>>> make.conf(5) is your friend. You should be able to add >>>> DEFAULT_VERSIONS+=rust1.76 >>>> to accomplish your task. NOTE you may want to comment this line later >>>> should it cause problems with other ports that aren't your current >>>> target. >>>> IOW your choices here should be chosen carefully and watched closely. >>>> It's >>>> easy to set it and forget it. :) >>>> To get the right permutation. Have a look in Mk/bsd.default-versions.mk >>>> -- >>>> --Chris Hutchinson >>> This is not correct. :/ >> I'm sorry to hear this. For the sake of clarity; Is this just my ignorance >> for rust? >> I have no difficulty accomplishing this task with other targets -- perl, >> php, *SQL,... >> So long as the *chosen* version is still available within the ports tree. >> Granted; >> this isn't a one-size-fits-all situation. Much the same as mixing ports && >> packages. >> But if carefully curated, has worked for me. > > The problem is that there is only one lang/rust. There are no > "versioned" port versions, like lang/phpXY, lang/pythonXYZ, etc. There > is a lang/rust-nightly port, but I don't think it is meant for general > consumption. > > That said, I don't know if it is technically possible to have more than > one rust port. I would guess the whole crate system depends on which > rust version built it? If so, you would also have to "flavorize" all > the rust crates and their sub-ports. > > It sounds like quite a lot of work, while in the mean time the rust > releases keep on coming fast. :) That makes perfect sense. Thanks for the clarification, Dimitry! :) > > -Dimitry -- --Chris Hutchinson