mingw-cross-env-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mingw-cross-env-list] On creating packages, source files and checks


From: Volker Diels-Grabsch
Subject: Re: [Mingw-cross-env-list] On creating packages, source files and checksums.
Date: Sun, 11 Aug 2019 11:42:25 +0200
User-agent: Mutt/1.10.1 (2018-07-13)

Dear Gregorio,

If I haven't missed a new feature in the MXE core, there's currently
no way to have multiple source file per package.

I believe in the past we solved similar issues as follows: Provide one
dummy-package per source file, so they are downloaded and checked. The
last ("main") package then depends on all others and performs the
actual build(s).

Alas, I wasn't able to find a concrete example of that approach at a
first glance.  But maybe you do.  However, it is also possible that
all packages which previously used the above approach were replaced by
separate builds which were percieved to be "cleaner".

If you don't want to go that route, I'd sugest to go your first
approach: I don't see a huge problem in keeping bootstrap compilers
around, as long as their binariy names are properly and consistently
prefixed.

Either way, if you have further questions, feel free to open an issue
tracker entry on that.  Maybe you'll get more/better responses there:

    https://github.com/mxe/mxe/issues


Regards,
Volker


Gregorio Litenstein schrieb:
> I am asking this again since it got lost/ignored last time.
> 
> Is it possible to create a package so that it downloads more than one
> source package?
> 
> The reason I'm asking is because I'm trying to port rust; the problem is
> rust requires a bootstrap compiler that cannot be built from scratch, we
> _need_ to either download it or provide it somehow. One possible solution
> of course would be to have a package for each bootstrap component (there's
> 3; rustc, rust-std and cargo). That would probably work but would mean
> keeping bootstrap compilers around on the system after building the real
> compiler so it's far from ideal.
> 
> Another solution maybe would be to make a single package containing both
> the source and the bootstrap binaries and host it somewhere; this is also
> not ideal because there would have to be one for each different OS
> supported by MXE.
> 
> The ideal solution of course, would be to be able to have more than one
> source file for a package. Then I'd be able to pull all required
> components, check their checksum and get rid of them once they're no longer
> needed.
> 
> Is that last option possible?
> 
> And, in case it's not; is it possible to get around the no-download thing
> (I know this is very discouraged but if there's no other solution...) I
> promise to be good and verify checksums for anything I download!
> 
> -- 
> Gregorio Litenstein Goldzweig
> [image: glit_ind.png]
> M├ędico Cirujano
> 
> 
> 
>    - Fono: +56 9 96343643 <+56%209%2096343643>
>    - E-Mail: address@hidden

-- 
Volker Diels-Grabsch
----<<<((()))>>>----



reply via email to

[Prev in Thread] Current Thread [Next in Thread]