Sebastien Marie - Sun, 26 April 2020 at 19:48:07
> On Sun, Apr 26, 2020 at 05:59:01PM +0200, f.holop wrote:
> > Stuart Henderson - Sun, 26 April 2020 at 16:30:32
> > > Don't list the main distfile (i.e. the port itself) in MODCARGO_CRATES.
> >
> > yes of course, don't touch yourself while time travelling :}
> >
> > now i get this:
> >
> > ===> Extracting for hyperfine-1.9.0
> > [modcargo] moving crates to
> > /home/f/src/ports/pobj/hyperfine-1.9.0/hyperfine-1.9.0/modcargo-crates
> > mkdir:
> > /home/f/src/ports/pobj/hyperfine-1.9.0/hyperfine-1.9.0/modcargo-crates: No
> > such file or directory
> >
>
> It could help if you look at some port using devel/cargo as example.
>
> you could see such lines in /usr/ports/textproc/ripgrep/Makefile:
>
> # as devel/cargo MODULES adds DISTFILES, GH_* didn't
> DISTFILES += ${DISTNAME}${EXTRACT_SUFX}
>
> the port itself needs to know what to download (DISTFILES) and have the list
> of
> crates used by it (MODCARGO_CRATES).
right.
yes, i saw that line in other ports. unfortunately the comment made
little sense to me as i dont have the rust porting experience of the
person who put it there.
is this always needed? only sometimes? which cases? why is it not
then in every cargo port?
is this something people trying to make rust ports will have to find
from mailing archives?
-f
--
