Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Writing packages #78

Open
infinisil opened this issue Jul 2, 2024 · 3 comments
Open

Writing packages #78

infinisil opened this issue Jul 2, 2024 · 3 comments

Comments

@infinisil
Copy link
Member

infinisil commented Jul 2, 2024

Let's package some packages, perhaps ones from the list of requested ones!

We will focus on this topic this week at Wednesday 16:00 CEST! If anybody has any specific requests, either:

  • Ask them in this issue in advance with a comment
  • Join the livestream and use the chat to ask questions live
@infinisil infinisil pinned this issue Jul 3, 2024
@infinisil
Copy link
Member Author

infinisil commented Jul 9, 2024

We will look at this topic again this week at Wednesday 16:00 CEST! If anybody has any specific requests, either:

  • Ask them in this issue in advance with a comment
  • Join the livestream and use the chat to ask questions live

@tcurdt
Copy link

tcurdt commented Jul 9, 2024

It seems like a nightmare to maintain the sha256 fields. What tooling is there to maintain those?

@pinpox
Copy link

pinpox commented Jul 10, 2024

I have a question for a package I'm working on: NixOS/nixpkgs#325824
This is a web-frontend (client) for a server application that you can self-host.

Upstream specifies that you can set an environment variable for the build, this "bakes in" the endpoint where the client application will then look for the backend.

Upstream built instructions say:

NEXT_PUBLIC_ENTE_ENDPOINT=http://mydomain.tld:8080 yarn build:photos

How would I package that for nixpkgs? an override? Not sure what the cleanest way would be to do this so the user can set the endpoint easily and it causes as little rebuilds as possible

@infinisil infinisil unpinned this issue Jul 16, 2024
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

No branches or pull requests

3 participants