zirias@
Developer
In the context of ports moving to GIT, as well as (expected) deprecation of portsnap, I've seen some questions regarding INDEX, which was automatically fetched by portsnap.
Right now, I learned the following in an IRC channel full of devs:
(anonymized the handle here and removed timestamps)
I just think anyone should be aware and think twice about using something that relies on INDEX.
Right now, I learned the following in an IRC channel full of devs:
Code:
< XXXXXX> INDEX is currently dangerously misleading, that needs to be fixed first
< XXXXXX> I looked into fixing it but given the dependencies between INDEX and portsnap it made sense to wait for portsnap to die first
< Zirias> I never use it anyways. But some workflows need it…
< Zirias> XXXXXX: what exactly is misleading? does it affect a locally created one?
< XXXXXX> currently the dependency info in it can be outright wrong due to failure to interpret flavors
< Zirias> uh!
< XXXXXX> it assumes it can take a port origin without flavor (i.e. cat/port rather than cat/port@flavor) and translate that to a package name
< XXXXXX> which is wrong
< Zirias> so it's essentially broken since flavors are supported? :o
< XXXXXX> yup
I just think anyone should be aware and think twice about using something that relies on INDEX.