Merge selectors crate with changes from gecko?

[devongovett]

It seems the selectors crate here (and published to crates.io) has diverged from the copy in gecko. For example, cssparser was updated to 0.29. Should the one in gecko be the one that is published to crates.io? Should the changes be merged back here? Which version is the canonical one?

I'm happy to send a PR to update cssparser in the crates.io released version but would like to understand the relationship between these two versions.

[emilio]

The crates.io version isn't even the servo/ version, it's the servo version with the MallocSizeOf stuff removed, IIRC.

I used to keep the Servo version periodically up-to-date, though I haven't done so in a while (I probably should).

[devongovett]

Ah. How does the crates.io version get updated? Is there another repo?

[cortesi]

I have a project that relies on selectors, and the lack of updates to the crates.io package is making things a bit harder than they need to be. We are also a little concerned that development momentum in servo has petered out, and that the bits we rely on might stagnate. I wonder if it's time to consider extracting selectors into a free-standing module that would be easier to move forward?

[paulrouget]

@emilio can you summarise the porting process from Gecko's version to a publishable version? I can take care of the migration if that's not too painful.