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

apache-httpd: Add 'extensions' config option for mediawiki #22236

Merged
merged 1 commit into from May 1, 2017

Conversation

Baughn
Copy link
Contributor

@Baughn Baughn commented Jan 28, 2017

Motivation for this change

Being able to add additional extensions.

Things done
  • Tested using sandboxing
    (nix.useSandbox on NixOS,
    or option build-use-sandbox in nix.conf
    on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • Linux
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

@Baughn Baughn changed the title apache-httpd: Add 'extensions' config option apache-httpd: Add 'extensions' config option for mediawiki Jan 28, 2017

buildPhase =
''
for skin in $skins; do
cp -prvd $skin/* skins/
done
for extension in $extensions; do
cp -prvd $extension/* extensions/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be better to have each extension in it's own store path and using symlinks here?

Also you don't need the /* if you are using -r.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be better, but I'm not familiar with mediawiki and don't know for certain that it'd accept symlinks. It might try to write to them.

As to the /*, note that $extension isn't a single extension; it's a directory containing extensions, which need to be copied including the directory name. That works the same way as for $skin, but if I changed it -- including by using a per-extension derivation -- I'd then need to pass the name of the extension out-of-band somehow.

Which might be fine if we had a complete list of them, but we don't. Today the way to add extensions to MediaWiki in NixOS is for the user to download them and put them in a directory... and that's probably fine.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not familiar with mediawiki

Well I presume you are testing this somehow? So if you can try and see if it works. I don't see why it wouldn't unless mediawiki was doing something quite odd.

It might try to write to them.

This won't be allowed in either case as the nix store is mounted read only.

As to the /*, note that $extension isn't a single extension; it's a directory containing extensions. ...

Ah, I see. That's fine then.

@cillianderoiste cillianderoiste merged commit 248a066 into NixOS:master May 1, 2017
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.

None yet

3 participants