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

intltool: refactor #7803

Merged
merged 1 commit into from
May 11, 2015
Merged

intltool: refactor #7803

merged 1 commit into from
May 11, 2015

Conversation

codyopel
Copy link
Member

No description provided.

wkennington added a commit that referenced this pull request May 11, 2015
@wkennington wkennington merged commit c3bdabc into NixOS:master May 11, 2015
@vcunat
Copy link
Member

vcunat commented May 11, 2015

I guess you know that most of the changed parts were generated from default.upstream? @7c6f434c should know more about it.

@wkennington
Copy link
Contributor

Yeah, I'm aware but not really sure how I feel about it :/. We probably need to discuss that style of automatic updating and packaging.

@codyopel
Copy link
Member Author

I suppose, but I haven't been able to completely figure out how update-walker.sh is supposed to be called and not many build make use of it.
https://github.com/NixOS/nixpkgs/blob/master/pkgs/build-support/upstream-updater/update-walker.sh

@vcunat
Copy link
Member

vcunat commented May 11, 2015

I've never used it myself; I just know it exists. A few other people also have their own generic updater scripts, and there's also nixpkgs monitor.

Perhaps one day we might agree on a common metadata format for these to unify what's committed into nixpkgs, i.e. standardize format that specifies how to determine whether an update is available, e.g. skipping unstable/testing updates and verifying crypto-signatures. Then we could have reliable automatic update detection for important packages.

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