Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 1 Jan 2024 01:34:13 -0800
From:      Yuri <yuri@FreeBSD.org>
To:        Alastair Hogge <agh@riseup.net>, freebsd-ports@freebsd.org
Subject:   Re: Rust/cargo dependencies
Message-ID:  <76c64ebd-0336-42a2-baad-1afa900ffda8@FreeBSD.org>
In-Reply-To: <2aa2dbd4f8d4e655cb74012bad6a6650@riseup.net>
References:  <2aa2dbd4f8d4e655cb74012bad6a6650@riseup.net>

next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
--------------O5TuFy9D0rML64otwEzHLGLj
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit


Hi Alastair,

The port devel/pylyzer appears to be very similar.
You can add setuptools-rust, USES=cargo, and then generate CARGO_CRATES 
using 'make cargo-crates.


Hope this helps,
Yuri


On 12/31/23 19:19, Alastair Hogge wrote:
> Hello, I am attempting to update security/py-bcyrpt to 4.1.2, however, 
> the Port now requires much oxidisation, and I am completely lost on 
> how to apply that. If I add cargo to ${USES}, then makesum and 
> cargo-crates both overwrite distinfo, removing the distfile 
> information for py-bcrypt. poudriere-testport will not complete 
> because the build wants to update some index via crates.io, and 
> network access is restricted during testport. I have had to set 
> ${CARGO_CARGOTOML}, however, that only works when ${USES} is not 
> populated with cargo. How does one configure the Port so ${WRKSRC} 
> stopped getting nuked and replaced with cargo-crates, and how can 
> testport continue without network access? -- To health and anarchy 
> Alastair 


--------------O5TuFy9D0rML64otwEzHLGLj
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix"><font face="monospace"><br>
      </font>
      <div class="moz-cite-prefix"><font face="monospace">Hi Alastair,</font></div>
      <div class="moz-cite-prefix"><font face="monospace"><br>
        </font> </div>
      <div class="moz-cite-prefix"><font face="monospace">The port <span
            style="color:#000000;background-color:#ffffff;">devel/pylyzer
            appears to be very similar.</span></font></div>
      <div class="moz-cite-prefix"><font face="monospace"><span
            style="color:#000000;background-color:#ffffff;">You can add
          </span><span style="color:#000000;background-color:#ffffff;"></span><span
            style="color:#000000;background-color:#ffffff;">setuptools-rust,
            USES=cargo, and then generate CARGO_CRATES using '</span><span
            style="color:#000000;background-color:#ffffff;">make
            cargo-crates.</span></font></div>
      <div class="moz-cite-prefix"><font face="monospace"><span
            style="color:#000000;background-color:#ffffff;"><br>
          </span></font></div>
      <div class="moz-cite-prefix"><font face="monospace"><span
            style="color:#000000;background-color:#ffffff;"><br>
          </span></font></div>
      <div class="moz-cite-prefix"><font face="monospace"><span
            style="color:#000000;background-color:#ffffff;">Hope this
            helps,</span></font></div>
      <div class="moz-cite-prefix"><font face="monospace"><span
            style="color:#000000;background-color:#ffffff;">Yuri</span></font></div>
    </div>
    <div class="moz-cite-prefix"><font face="monospace"><br>
      </font></div>
    <div class="moz-cite-prefix"><font face="monospace"><br>
      </font></div>
    <div class="moz-cite-prefix"><font face="monospace">On 12/31/23
        19:19, Alastair Hogge wrote:<br>
      </font></div>
    <blockquote type="cite"
      cite="mid:2aa2dbd4f8d4e655cb74012bad6a6650@riseup.net">Hello,
      I am attempting to update security/py-bcyrpt to 4.1.2, however,
      the Port
      now requires much oxidisation, and I am completely lost on how to
      apply
      that. If I add cargo to ${USES}, then makesum and cargo-crates
      both
      overwrite distinfo, removing the distfile information for
      py-bcrypt.
      poudriere-testport will not complete because the build wants to
      update
      some index via crates.io, and network access is restricted during
      testport. I have had to set ${CARGO_CARGOTOML}, however, that only
      works
      when ${USES} is not populated with cargo. How does one configure
      the
      Port so ${WRKSRC} stopped getting nuked and replaced with
      cargo-crates,
      and how can testport continue without network access?
      --
      To health and anarchy
      Alastair
    </blockquote>
    <p><br>
    </p>
  </body>
</html>

--------------O5TuFy9D0rML64otwEzHLGLj--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?76c64ebd-0336-42a2-baad-1afa900ffda8>