.dep-files can't contain path

[uggla]

Hi!

A dependency in a .dep-file can't have a path but an item in a .lst-file can.

The line bellow works in a .lst-file but not in a .dep-file.

subdir/programname.tcz

[Jason W]

Correct.

[Jason W]

More specifically, there is likely not much demand to support the ability to include in a dep file the full path to an extension outside of the tce directory since that would slow things down for everyone while providing a desired feature for a very few.  That would likely only be used for testing purposes, and when testing there are usually several ways to achieve what is desired within the existing framework.

[uggla]

It would make it possible to organize extensions for special purposes. But if there is no demand and it would slow things down then its not worth it.

regards
Uggla

[bmarkus]

It would make it possible to organize extensions for special purposes. But if there is no demand and it would slow things down then its not worth it.

regards
Uggla

I'm using different sets of extensions for different purposes. I have /tce, /tce3, /tce4, ... folders on either USB stick or HD and specifying TCE dir in command line.

It works fine using current toolset and features.

[uggla]

Yes, but that means a lot of duplicates.

[bmarkus]

Yes, but that means a lot of duplicates.

An extension set is ralatively small, while storage is really cheap. For sure cheaper tha labour cost of development

[curaga]

Symlinks have been used for that purpose. Hard links would work too.

[uggla]

Symlinks have been used for that purpose. Hard links would work too.

Ok, but what happens when updating extensions? Links get overwritten, right?

[tinypoodle]

Symlinks have been used for that purpose. Hard links would work too.

Note: This requires tce_dir being on a filesystem capable of linking, e.g. FAT* would be out of the question.