Remove option-ext dependency

[kpcyrd]

I found a way to replace the use of this dependency with a trivial compare.

[soc]

Sorry, but I like it the way it is.

[kpcyrd]

Why?

[AlexTMjugador]

A dependency for such a trivial operation is rather on the bloatful side, but most importantly, extends the virality of its copyleft MPL license to this MIT/Apache-licensed crate, which does not make much sense:

Can this decision be reconsidered, please? This alone is a reason to stay on dirs v4, which did not have this transitive dependency.

Edit: @kpcyrd, the reason @soc mentioned for this being the way it is can be read here: e169da7#r109131407

[kpcyrd]

I noticed this PR is an exact duplicate of #24.

[soc]

@AlexTMjugador extends the virality of its copyleft MPL license

?

[AlexTMjugador]

@AlexTMjugador extends the virality of its copyleft MPL license

?

I wrote that comment before properly researching the situation with this dependency. At the moment, I have no new arguments to add to the discussion about why the dependency on option-ext is, in my opinion, uncomfortable. Other people have already thoroughly explained reasons I can think of in several other issues.

[nihohit]

I'd like to join the request - my org forbids the usage of crates using a copyleft license even as an indirect dependency.
@soc I understand that you prefer the code as is, I just hope that you understand that this makes dirs-sys and crates dependent on dirs-sys unusable by some organizations.

[soc]

@nihohit That's fine. Orgs that object even to the tiniest bit of responsibility are "customers" that I can easily do without.