News for hackers. Stuff that matters.
Re:There is no such thing as a “glibc based alpine image” by ricardobeat on Thursday August 26, 2021 @09:31AM (#28314668)
This post would have done fine without the whole “we do not approve” / “we need to take them down” attitude.

Call it a terrible idea, explain why, recommend against it, and be done with it; one shouldn’t need approval to maintain a fork, and they are not misrepresenting what it is. I find the animosity a little off-putting.

Re:There is no such thing as a “glibc based alpine image” by r1ch on Thursday August 26, 2021 @09:54AM (#28314963)
I think this comes from them using "Alpine" in the name for something that is not from the Alpine Linux team nor desired / supported by them. Users could be confused into thinking it's something officially supported and clog up official support channels with unrelated issues.
Re:There is no such thing as a “glibc based alpine image” by sgerrand on Thursday August 26, 2021 @11:35AM (#28316248)
Maintainer of the Alpine package you referenced here. I'm not a "them". ;)

I don't see where "Alpine" is used in the package name, unless you're referring to the source repository name. In case it isn't clear, `alpine-pkg-` is a prefix which denotes that the repository contains an Alpine Linux package manifest and configuration. There's nothing in the repo itself which states that this package is published and/or endorsed by Alpine Linux.

Re:There is no such thing as a “glibc based alpine image” by gnud on Thursday August 26, 2021 @11:54AM (#28316554)
Re:There is no such thing as a “glibc based alpine image” by sgerrand on Thursday August 26, 2021 @12:27PM (#28317041)
Ah, thanks for the pointer. The blog post referenced the Alpine package I maintain but was obviously implicitly referencing those Docker images.
Re:There is no such thing as a “glibc based alpine image” by ariadneconill on Thursday August 26, 2021 @05:38PM (#28321204)
Yes, there's several of them. The problem isn't your package, but the distribution of "alpine" images that integrate the package. Those images should describe themselves more appropriately.
Re:There is no such thing as a “glibc based alpine image” by stonemetal12 on Thursday August 26, 2021 @02:04PM (#28318345)
It uses "glibc" in the name, should we assume it is an official glibc project? Perhaps by using both in the name we should assume it is an official announcement that glibc and alpine Linux have merged and are now one and the same thing!

Or perhaps we should not be dumb and see that it doesn't come from the official channels of either. Therefore we should assume it is some random project that tries to use both, however poor an idea that maybe.

Re:There is no such thing as a “glibc based alpine image” by MrStonedOne on Thursday August 26, 2021 @10:36AM (#28315497)
Alpine is free to provide a solution to the problem then.

Complaining about the problem isn't going to be productive, and until they publicize a way to convey you are a fork of the alpine project they will have this issue.

Welcome to FOSS.

xchat solved this with ychat.

Re:There is no such thing as a “glibc based alpine image” by undecisive on Thursday August 26, 2021 @11:10AM (#28315941)
> Alpine is free to provide a solution to the problem then.

Alpine is also free to _not_ provide a solution to the problem.

Alpine is free to say "This is not an approved use of our name"

As you point out, the way to convey that you are a fork is to change your name in a non-confusing way, and provide attribution to the original in your readme or licenses.

Re:There is no such thing as a “glibc based alpine image” by encryptluks2 on Thursday August 26, 2021 @01:54PM (#28318211)
This isn't a fork. I seriously wonder how many people here are commenting without having any clue as to what they are talking about. It is simply a package that you install with apk in Alpine.
Re:There is no such thing as a “glibc based alpine image” by undecisive on Friday August 27, 2021 @07:05AM (#28326305)
Thanks for your "clarification", however I don't think you've fully grokked the situation yourself.

I think the thing that was referred to as a "fork" was the docker image, which uses the package you mention, and afaik is the primary way that people are receiving that package and believing it to be blessed by the Alpine gods. In the sense that the container is a distribution in its own right that deviates from the roadmap of the Alpine makers, it could be considered a fork of sorts. And given that the package naming is far less confusing than the dockerhub naming, I feel like that's what most people on HN are attributing the confusion to.

Note that the article doesn't mention that it's the container that is the source of confusion until the very last section, where it points out what they want to rename. The package itself is called alpine-pkg-glibc and as the author of that package has pointed out, the reason it is called that is to follow alpine package naming conventions, and they have mentioned on this HN convo that they are completely open to changing that name if asked.

But regarding the docker image, I'm well aware that this isn't technically a full fork; I was mirroring the language used on the parent poster - however, since your clarification does not do justice to the complexity of the situation either and implies that you have less clue about what you're talking about, maybe tone it down a bit. Especially since one possible solution to this situation is indeed for the frolvlad/alpine-glibc authors to produce a full fork of Alpine linux with glibc and call it something else (I wonder if Himilayan Linux is available?)

Re:There is no such thing as a “glibc based alpine image” by encryptluks2 on Saturday August 28, 2021 @06:45PM (#28342210)
So, let's say I create a Docker Hub image with alpine as the base, then I install a package from the Alpine repo.. let's say Chromium. So now you're telling me, that is a fork of Alpine and I should be forced to recompile Alpine entirely anytime I want to install a package and create a Docker Hub image? I guess that is one way to ensure no one uses Alpine for container images ever again.
Re:There is no such thing as a “glibc based alpine image” by undecisive on Tuesday August 31, 2021 @04:30AM (#28365243)
I'll be boring and ignore the straw man if you don't mind, and continue to focus on the theme of "people here are commenting without having any clue as to what they are talking about"

> then I install a package from the Alpine repo

You might want to do some research - from the readme: "The current installation method for these packages is to pull them in using wget or curl and install the local file with apk" - https://github.com/jeanblanchard/docker-alpine-glibc/blob/ma... <- That dockerfile, for example, installs curl using the normal Alpine repos, then uses curl to download the signing keys and the packages for the glibc package.

But yes, if someone builds a chrome package that completely screws up other packages in alpine, to the point that the Alpine maintainers are being inundated with bogus support requests then yes, ONE SOLUTION is to recompile the project in a way that means that the package is no longer a problem. You have solved the problem with a fork.

The other solution is to make it very very clear in your naming and documentation that this is not a supported alpine image, and that bug reports should go to the maintainer of the image, not Alpine themselves.

However, either way, you could be argued to have created a new "distribution" of software that is no longer truly Alpine linux, but is based on Alpine linux. Including Alpine in the name is not necessary, and in this case it seems, not desirable.

Even if your codebase is not a fork, you have "forked off" from the original distribution.

Re:There is no such thing as a “glibc based alpine image” by dralley on Thursday August 26, 2021 @10:59AM (#28315782)
> Alpine is free to provide a solution to the problem then.

This entire post is about how there isn't a solution to that problem. It's a fundamentally flawed idea.

Re:There is no such thing as a “glibc based alpine image” by MrStonedOne on Thursday August 26, 2021 @11:08AM (#28315914)
The solution is to seperate the branding from the idea. There is no way for somebody to suggest in the name of their product that they are a downstream of alpine without using the word alpine. alpine linux can fix this by creating and providing a generic word for their flawed-opinionated-mini-linux whatever
Re:There is no such thing as a “glibc based alpine image” by deadbunny on Thursday August 26, 2021 @12:03PM (#28316707)
> alpine linux can fix this by creating and providing a generic word for their flawed-opinionated-mini-linux whatever

Why is it on the Alpine Devs to name a downstream project? Would you ask the Debian devs to name Ubuntu?

Re:There is no such thing as a “glibc based alpine image” by encryptluks2 on Thursday August 26, 2021 @01:56PM (#28318240)
It isn't even really a downstream project. This is like saying that third party Deb packages are downstream projects of Debian. They are just third-party packages you can install in Debian.
Re:There is no such thing as a “glibc based alpine image” by MrStonedOne on Thursday August 26, 2021 @12:13PM (#28316861)
they are the ones who have an issue with alpine-glibc's name
Re:There is no such thing as a “glibc based alpine image” by hvs on Thursday August 26, 2021 @11:12AM (#28315971)
The post has a section called "Alternatives to alpine-glibc"
Re:There is no such thing as a “glibc based alpine image” by minxomat on Thursday August 26, 2021 @10:37AM (#28315504)
The proposed solution here is to prevent installation of the package, which is a valid solution. You can still set it up if you want, but Alpine isn't going to let you footgun yourself so easily.

Homebrew does the same: https://github.com/Homebrew/brew/blob/3476ca7b8ff889ef61e657...

Exclusions for compatibility and security reasons are not the same as "taking them down". It's linux after all.

Re:There is no such thing as a “glibc based alpine image” by lalaithion on Thursday August 26, 2021 @10:47AM (#28315648)
The only reason to have the "we need to take them down" attitude would be if they are violating your license or glibc's license.
Re:There is no such thing as a “glibc based alpine image” by lalaithio-glibc on Thursday August 26, 2021 @11:00AM (#28315792)
Using the same name can also be considered inapproriate.
Re:There is no such thing as a “glibc based alpine image” by sgerrand on Thursday August 26, 2021 @11:36AM (#28316275)
Maintainer of the Alpine package referenced here. The same name for what? The package name is `glibc`. I think you're confusing/conflating the source control repository's name with the package when they are different things.