Information regarding upcoming Gitlab Migration: clarifications
nate-RoXCvvDuEio at public.gmane.org
Fri May 1 14:13:36 BST 2020
On 4/30/20 11:17 PM, Ben Cooksley wrote:
> Not necessarily.
> Git allows you to override the name that the local folder is called
> when cloning, so there is no reason why we can't specify something in
> the metadata to override the local name that the folder gets called in
> your local checkout folder.
> This would allow for example:
> - frameworks/kcoreaddons on Gitlab continues to be called
> 'kcoreaddons' in your local checkout folder
> - maui/dialer on Gitlab gets called 'maui-dialer' in your local checkout folder
> This allows for the URLs on Gitlab to make sense, while simultaneously
> allowing your local source checkout folders to continue to work in the
> manner in which they do currently.
> Note that we do not expect people to hit this in many cases - this is
> about giving us the flexibility for the long term without imposing
> unnecessary bureaucracy and limits on projects within the KDE
> Automated tooling such as kdesrc-build and the proposed clone script
> (that searches in namespaces) should be able to handle this without
> much issue.
> In the case of manually done clones, it is reasonable to expect people
> to know what they're doing with their clones, and name them
> appropriately in the event they have a collision.
> Does this sound acceptable?
A little weird, but probably acceptable. I suppose it's no worse than
having discover build an executable called "plasma-discover", which
trips me up like five times a day :)
More information about the kde-core-devel