feat: support scheme 'file' to process local conda files

[amamiya-len]

Motivation

In my situations, I made some private packages locally and add dependencies with 'file' URLs in pixi.toml(actually pixi support 'file' URLs), but it seems that pixi-pack doesn't support 'file' URLs. So I add support for scheme 'file'.

Changes

Just changed function download_package.

[delsner]

Thanks for your contribution! Could you please add an integration test for this feature? You can add a new example for this.

[delsner]

This seems fishy. Why do we need it and why using the current working directory as default? Shouldn't we rather fail in these cases?

[amamiya-len]

Thanks for your contribution! Could you please add an integration test for this feature? You can add a new example for this.

I ran integration tests but only 3 tests passed(main branch and my PR are the same). I searched for the environment about integration tests but didn't find it. Could you please provide me with detailed instructions?

[pavelzw]

in https://github.com/Quantco/pixi-pack/blob/19c4b336f37c8c11de467ce058cf846de589d536/tests/integration_test.rs you can find some integration tests, just adding another one that covers your use case should be fine

[amamiya-len]

in https://github.com/Quantco/pixi-pack/blob/19c4b336f37c8c11de467ce058cf846de589d536/tests/integration_test.rs you can find some integration tests, just adding another one that covers your use case should be fine

Alright, I will add a new integration test and rethink the implementation of download_package function

[amamiya-len]

I encountered a problem: file URLs only supports absolute paths, and I need to dynamically generate pixi.toml and pixi.lock according to the project path. I don't know how to gracefully do it. Do you have any idea?

[pavelzw]

@amamiya-len i pushed an integration test that just templates the pixi.toml

[amamiya-len]

OK,I see. I was a little busy days ago.