Re: The case for moving raw binaries

[Liliana Marie Prikler]

Am Donnerstag, dem 28.04.2022 um 21:57 +0200 schrieb Maxime Devos:
> Liliana Marie Prikler schreef op do 28-04-2022 om 19:27 [+0200]:
> > > How does this help with double wrapping?  Whether the wrappers /
> > > originals are put in /bin or $RAWBIN_DIR, it's still wrapped twice.
> > Because $RAWBIN_DIR can be ignored when wrapping.  This means that
> > stuff that's already in it won't be added again.
> > [...]
> > Constructing the wrapper is not so much the problem, it's not
> > wrapping the already wrapped binaries. 
> 
> Why can $RAWBIN_DIR be ignored when wrapping?  If the build system just
> sets $X during its wrappers, but the application needs $Y as well
> (wrapped in a build phase), then if the extra wrapping is cancelled,
> then the application won't get its $Y variable, which seems like a bug
> to me.
The extra wrapping isn't cancelled though?  You just append the
definition of $Y to the the already existing definitions, but you don't
move the wrapper to $RAWBIN_DIR, because the actual binary already
exists there.

In other words, you have after wrap:
- bin/foo ~> rawbin/foo
and after wrap-again
- bin/foo ~> rawbin/foo
where ~> is the wrapping relation.

Currently, you have after one wrap
- bin/foo ~> bin/.foo-real
after two
- bin/foo ~> bin/.foo-real
- bin/.foo-real ~> bin/..foo-real-real
after three
- bin/foo ~> bin/.foo-real
- bin/.foo-real ~> bin/..foo-real-real
- bin/..foo-real-real ~> bin/...foo-real-real-real
and so on.

Is this clearer now?

Cheers