libelektra icon indicating copy to clipboard operation
libelektra copied to clipboard

Fixed path for bootstrap file

Open markus2330 opened this issue 3 years ago • 1 comments

This issue is about a proposal to introduce default mountpoints via the normal mount mechanism and disable the current "default mountpoints" (replace by using an error plugin, which cannot be used by accident). It is not about improvements of the bootstrapping. Please open a different issue if you want to discuss these parts.

Okay, but you started by referencing one of my comments. In that comment my goal was not to change the current default mountpoint setup, but to separate the bootstrap backend. So I continued my comments from there....

It is very fixed (can only be changed via symlinks).

There is still quite a few moving parts. For example, the bootstrap file is not defined by an absolute path.

And yes, you can always swap the shared libraries. But what I dislike is that by using symlinks we kind of encourage it. This makes it seem like using a different setup for bootstrap might be supported. That's exactly what I want to avoid, since supporting such a thing would be a nightmare.

Originally posted by @kodebach in https://github.com/ElektraInitiative/libelektra/issues/4446#issuecomment-1229250068

markus2330 avatar Aug 28 '22 07:08 markus2330

There is still quite a few moving parts. For example, the bootstrap file is not defined by an absolute path.

Yes, I agree. It would make the bootstrap and the CMake setup much simpler.

Which file should we hardcode to be used for bootstrapping?

My preferences would be:

  • /etc/elektra/bootstrap.ecf
  • /etc/kdb/elektra.ecf (most compatible with status quo)
  • /etc/elektra.ecf (creates too much clutter in /etc if we come up with further files)
  • other suggestions?

And yes, you can always swap the shared libraries. But what I dislike is that by using symlinks we kind of encourage it. This makes it seem like using a different setup for bootstrap might be supported. That's exactly what I want to avoid, since supporting such a thing would be a nightmare.

So you want that we remove these two symlinks and we hard-code specific names for resolver and storage in the "bootstrap backend"?

Btw. @kodebach creating new issues from existing ones is just one click.

markus2330 avatar Aug 28 '22 07:08 markus2330

I mark this stale as it did not have any activity for one year. I'll close it in two weeks if no further activity occurs. If you want it to be alive again, ping by writing a message here or create a new issue with the remainder of this issue. Thank you for your contributions :sparkling_heart:

github-actions[bot] avatar Aug 29 '23 01:08 github-actions[bot]

I closed this now because it has been inactive for more than one year. If I closed it by mistake, please do not hesitate to reopen it or create a new issue with the remainder of this issue. Thank you for your contributions :sparkling_heart:

github-actions[bot] avatar Sep 13 '23 01:09 github-actions[bot]