Reading wrong filepath for IFC Link library

[myoualid]

In testing whether we can ship IFC & blend files that contain ifc links using relative paths overall:

Scenario: (see folder structure below)
I start a new project.
I link an IFC project through a .blend file, using relative_paths.
I save my blender project.
I save my IFC file as a relative path.
I duplicate my folders.
I open my duplicated .blend file

--> The duplicated my_project.blend file reads the IFC Linked file from the path C:/my-project/REF/reference.blend instead of C:/my-project-copyt/REF/reference.blend. Probably because that's what stored in the Blender file that was copied.

Folder Structure:

main folder
└───my-project
│   │   my_project.blend
│   │   my_project.ifc
│   │
│   └───REF
│       │   reference.blend
│       │   reference.ifc
│   
└───my-project-copy
    │   my_project.blend
    │   my_project.ifc
    │ 
    └───REF
        │   reference.blend
        │   reference.ifc

[sboddy]

Confirmed still an issue:

On a theoretical different system (i.e. the path to the original project does not exist) the error would look like:

(I just move the original my-project folder.)

[Moult]

This works for me. @sboddy are you sure you enabled relative paths when linking the .blend?

[sboddy]

Maybe I'm misunderstanding his instructions. I originally tried making the link with the Project Setup -> Links -> Link IFC, and I am using the Use Relative Path option. I still get the original path in the copied folders my-project.blend when opened, as per the above screenshot.

Rereading his instruction "I link an IFC project through a .blend file, using relative_paths." I supposed he could have meant to File -> Link the relative.blend file, which also has a Relative Path option. However I just get an odd error preventing that from working:
'/home/steve/Documents/Blender/BonsaiBIM/Testings/test_3663/my-project/REF/reference.blend': cannot use current file as library
which is strange because it is not my current file.

I'll try to amend his instructions as I understand them, maybe you can see the where I've misunderstood:

Scenario: (see folder structure in OP)
I start a new project.
I save blend file as my-project/REF/reference.blend
I save IFC file as my-project/REF/reference.ifc

I start a new project.
I link an IFC file my-project/REF/reference.ifc to my new project with Project Setup -> Links -> Link IFC
I make sure to set Use Relative Path in the dialog.
I save blend file as my-project/my-project.blend (there is no obvious relative path option here)
I save IFC file as my-project/my-project.ifc
I make sure to set Use Relative Path in the dialog.

I recursively duplicate my-project folder to my-project-copy.
I open my duplicated my-project-copy/my-project.blend file.
Examine the Project Setup -> Links entry.
It shows /my-project/ in the linked IFC path, not /my-project-copy/

[sboddy]

Doh!!!! I see the problem (at least in my instructions - @myoualid will have to speak for themself). If you try to link the IFC file before you have saved the newly created my-project file, of course the system doesn't know what it is relative to. So the path is stored in full. Once saving the file first, the path is properly relative:

Maybe there should be a check/warning that the path will be absolute if the current file has not been properly saved.

[sboddy]

Closing this issue, as the problem was fixed.