----- Original Message -----
>
> >> build: cater for builds with latest vector (now 1.0.2)
> > It would have been helpful to discuss this first.
You and I discussed this on IRC months ago, went something like:
nathans> I don't think its a good idea to copy all of Vector into webjs
nathans> that's just going to cause double handling, surely
nathans> likely to cause an out of date second copy
nathans> and martin's keen to release it independently, which is cool
fche> people should be able to get everything in one download
nathans> wait... what? why?
fche> double handling is not going to be a problem, can be scripted
[fche commits it all into webjs anyway, end of discussion]
[nathans shrugs, moves on]
Fast forward several months and sure enough, we have an outdated copy
of Vector in the rpms (v1.0.2 tagged >2 months ago), noone has updated
the second webjs copy in a timely fashion, and noone is pushing latest
Vector code into rawhide.
So, we tried it one way and that had the predicted issues; let's try it
the other way and see if that helps us do a better job of keeping track
of upstream Vector releases.
> How well tested is it?
Works nicely for me, tested it a fair bit yesterday to double check
but I think trusting Martin's when-to-release judgement is the best
strategy for the RPMs we build.
> e.g., on F21 Firefox it doesn't run well.
>
> https://github.com/Netflix/vector/issues/83
I'm sure it will get resolved soon - we'll pick up the fix as soon as
there's a release with that available (and sooner on rawhide, via the
master branch pull in scripts/spin-rawhide now).
cheers.
--
Nathan
|