Skip to content

Don't use lsb_release to find platform - #1004

Merged
pivotal-david-osullivan merged 1 commit into
mainfrom
no-lsb-release
Mar 22, 2023
Merged

Don't use lsb_release to find platform#1004
pivotal-david-osullivan merged 1 commit into
mainfrom
no-lsb-release

Conversation

@ryanmoran

Copy link
Copy Markdown
Contributor

No description provided.

@pivotal-david-osullivan
pivotal-david-osullivan merged commit a7b0b1b into main Mar 22, 2023
@ryanmoran
ryanmoran deleted the no-lsb-release branch March 22, 2023 16:59
@anthonydahanne

Copy link
Copy Markdown
Contributor

hello @ryanmoran - doesn't your change mean that if the underlying platform is neither redhat based nor ubuntu based, the platform will not be determined? ie: alpine, debian, etc. won't be recognized as valid platforms anymore.

Actually, is that an issue? I'm asking cause I got bit by this change while running the tests in a container based on debian

@ryanmoran

Copy link
Copy Markdown
Contributor Author

Yes. I think the open question here is whether or not the buildpack needs to support these other OSes given that we basically only ship Ubuntu through the cflinuxfs* stacks.

@anthonydahanne

Copy link
Copy Markdown
Contributor

yeah, fair enough, That makes sense, thanks.

ramonskie pushed a commit that referenced this pull request Dec 4, 2025
Don't use lsb_release to find platform
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants