Re: Rakudo has a transition tracker and then what ?
Hi Sebastian,
Building the files upon installation is exactly the original
behavior. The problem is that compilation speed is too slow.
Three raku packages could take more than 2 minutes every
time when there is a raku upgrade to any version.
On Fri, 2022-02-04 at 13:55 +0100, Sebastian Ramacher wrote:
> On 2022-02-03 17:58:24, M. Zhou wrote:
> > @dod: It looks that we have to change the Architecture: of raku-*
> > packages into any (instead of "all") because there is no binnmu
> > for Arch:all package. Then upon each time we bump the rakudo API
> > version, we just need to file a regular transition bug to the
> > release team and trigger the rebuild.
>
> If the pre-compiled files are like pyc files for Python, is there are
> a
> reason to not follow the same approach? That is, build the pre-
> compiled
> files on install.
>
> Cheers
>
> >
> > On Thu, 2022-02-03 at 19:13 +0100, Jonas Smedegaard wrote:
> > > Quoting Paul Gevers (2022-02-03 19:08:34)
> > > > On 03-02-2022 18:53, Dominique Dumont wrote:
> > > > > Hoping to automate this process, I've setup a transition
> > > > > tracker
> > > > > for Rakudo
> > > > > [1].
> > > >
> > > > See
> > > > https://lists.debian.org/debian-release/2022/02/msg00029.html a
> > > > nd
> > > > follow-up messages.
> > >
> > > As I understand it, librust-* packages are released as arch:any
> > > (not
> > > arch:all) for this exact reason (I seem to recall some discussion
> > > with
> > > the ftpmaster and/or release team about that - evidently leading
> > > to
> > > that
> > > praxis being tolerated, except I am totally wrong and the cause
> > > for
> > > Rust
> > > is a different one).
> > >
> > >
> > > - Jonas
> > >
> >
> >
>
Reply to: