Skip to content

Package name: xkbcommon versus libxkbcommon, including the default archive distributed by the github project here #953

@rubyFeedback

Description

@rubyFeedback

Hey folks,

This is not a very important topic, but nonetheless I wanted to raise it. I will explain why in a moment.

The issue is:

We can download a stable tarball release, e. g. a .tar.gz file, such as this one here:

https://github.com/xkbcommon/libxkbcommon/archive/refs/tags/xkbcommon-1.12.0.tar.gz
wget https://github.com/xkbcommon/libxkbcommon/archive/refs/tags/xkbcommon-1.12.0.tar.gz

Now, when we extract it, we actually get this directory:

libxkbcommon-xkbcommon-1.12.0

This name is wrong, in my opinion. The best assumption is that the name of the tarball at hand,
becomes the very same name as the extracted directory. So the correct name should be:

xkbcommon-1.12.0

I assume github does this automatically, but I think it is also possible to change it; I know that
other projects follow this convention of package_name.tar.xz -> package_name, so I think
github prepends the project name to the tarball. I am not sure where this can be changed,
but since other projects manage this, I think it is possible and should be changed, for
simplicity and consistency reasons.

But this is the small thing; I don't think I would have created an issue for this (or perhaps I
did in the past, I am losing track of things I did...)

The thing to me is ... what is the name of the project? Is it "libxkbcommon" or "xkbcommon"?

I believe the old name was xkbcommon. Wasn't it hosted at https://www.x.org/releases/individual/?
I am not entirely certain anymore. The reason I assumed the name was xkbcommon was because
I used to track this program in the past, with a set of scripts; but it seems the name is indeed
libxkbcommon now, so I need to rename it locally. Which of course is trivial; the confusion I have
is more what the name really is. Right now I'll go with "libxkbcommon", but even this is not
100% consistent with the current README you guys are using. Let me give one example.

You folks write in the README this here:

"An project’s homepage can be found at https://xkbcommon.org/.

xkbcommon is maintained in git at: https://github.com/xkbcommon/libxkbcommon"

So this is interesting, because you write "xkbcommon is maintained" rather than
"libxkbcommon is maintained"; yet the URL ends with "libxkbcommon".

The URL at https://github.com/xkbcommon/ only has two entries - one is for
the homepage, the other one is for "libxkbcommon". I guess the name of the
library is "libxkbcommon", but the project name is xkbcommon. But would it
then not make more sense to write e. g.:

"libxkbcommon is maintained in git at: https://github.com/xkbcommon/libxkbcommon"

?

Anyway. I just wanted to point this out. I am fine either way, but the less confusion
the better, IMO. I think I first tracked xbkcommon many years ago, so I am not
always 100% up to date with upstream changes. Cheers!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions