confused by relative paths and sources.txt recursion

[kowey]

Suppose I have three packages: foo, subfoo, bar

The sources.txt for foo looks like this:

.
./subfoo

(subfoo is a sub-package in the foo family, let's say)

The sources.txt for bar looks like this:

 .
 /path/to/foo

Should subfoo be installed or not? Right now, it isn't and I have to write my bar sources.txt like this instead:

 .
 /path/to/foo
 /path/to/foo/subfoo

Apologies if this is documented and I just missed it!

[gregwebs]

subfoo should be picked up & installed, so this does seem like a bug. As per my comment in the other ticket, can you update your shelly (and cabal-meta) dependency to the latest and let me know if this issue still occurs?

[kowey]

When you say latest, do you mean the GitHub versions? (I ran into these issues on 20 Aug with a new HP install + new packages on top of that). Shelly.hs on GitHub doesn't seem to have commits newer than that. I think I'm using the latest cabal-meta from hackage.

[gregwebs]

no, not github. what version of the shelly package do you have?

[kowey]

cabal-meta-0.2.3.2
shelly-0.14.0.1
system-fileio-0.3.9
system-filepath-0.4.6
unix-compat-0.3.0.1

[gregwebs]

k, looks like you are on the latest :)

[gregwebs]

@kowey are you still seeing these issues after your cleanup?

[kowey]

Still seeing them.