| Commit message (Collapse) | Author | Age |
| |
|
|\
| |
| | |
lite: init at 1.03
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
There are a number of derivations failing because we are lacking the
required certs.
fetchurl is already ignoring certs so I figured we'd do the same.
|
| | |
|
| |
| |
| |
| |
| | |
The option "--skip-getting-started" no longer exists in vscode and causes files in "$@" to not be opened.
Message from stdout: "Warning: 'skip-getting-started' is not in the list of known options, but still passed to Electron/Chromium."
"--skip-getting-started" being removed: https://github.com/microsoft/vscode/commit/6a8b201c8aff79ae04d69038e815500a04f06401
|
| | |
|
| | |
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
As per reasonable suggestion, instead of extensively patching the
hboetes version of mg to work on MacOS using bits from ibara's mg,
just set upstream to ibara's mg.
This also removes the dependency on libbsd, although I'm not sure
if this is a good or bad thing.
|
| | |
| | |
| | |
| | | |
remove temporary files
|
| | |
| | |
| | |
| | |
| | |
| | | |
The actual most recent version is 20200215, so update the package version to this.
Furthermore, update the patch accordingly so it still builds. This adds back the
reallocarray.c file.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I am not happy with this at all. It avoids using libbsd at all on
darwin because there are conflicting header files, particularly the
header string.h.
Ideally that would be the thing to fix. But in the meantime, this patch
should do the trick.
It declares a header file apple.h, which files include if target is
darwin (checks for presence of __APPLE__). This header file also
references the three source files futimens.c, reallocarray.c and
strtonum.c. The former and latter are from https://github.com/ibara/mg
which is another portable fork, but building against more platforms.
From the OpenBSD source tree is _null.h and tree.h. There is a check so
that if __APPLE__ is present then it will include them from this source
tree.
Now,the makefile GNUMakefile will not link against libbsd on darwin, by
checking the output of uname in much the same way as it did already for
FreeBSD.
|
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| | |
@the-kenny did a good job in the past and is set as maintainer in many package,
however since 2017-2018 he stopped contributing. To create less confusion
in pull requests when people try to request his feedback, I removed him as
maintainer from all packages.
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
kdev-python: 5.5.0 -> 5.5.1
|
| | | |
|
|\ \ \
| | | |
| | | | |
kdevelop-unwrapped: 5.5.0 -> 5.5.1
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
kdev-php: 5.5.0 -> 5.5.1
|
| |/ / |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
macvim: 8.2.319 -> 8.2.539
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
MacVim compiles the Vim part using `/usr/bin/clang` and the GUI part
using Xcode. The Xcode portion always uses Xcode's own SDK and we have
no workable alternative. The Vim portion so far has been compiling using
a hybrid compilation environment, where it uses the SDK for most stuff
but picks up a bunch of library linker paths (including libSystem) by
virtue of Ruby's LDFLAGS. This hybrid compilation environment meant that
if the SDK headers referenced a symbol that the library itself didn't
have, this could produce link errors.
Previously we attempted to fix this by synthesizing an include path that
contained just the one header from Nix's Libsystem that referenced the
missing symbol, to get rid of the reference and allow linking to work
again, but this was very hacky and runs the risk of future Xcode SDK
changes producing the same errors with different headers, or of future
SDK versions expecting the intercepted header to contain a definition
that Nix's doesn't.
This new approach is to just clean up the compilation environment such
that the Vim portion is compiling against the Xcode SDK as well, by
sanitizing the LDFLAGS produced by the configure script so it stops
referencing Nix's versions of OS libraries. This means the resulting Vim
binary no longer depends at runtime on Nix for anything except the
scripting language support, but that's how it's been for the MacVim
binary all along anyway, and this approach should keep us insulated
against future Xcode SDK changes.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Xcode 11.4 has an updated sys/_types/_fd_def.h header that references a
new symbol from libSystem. This is a problem because we're using
`/usr/bin/clang` to compile the non-Xcode portion, and this pulls in
headers from Xcode's SDK. Somehow it's still linking to the Nix
libraries (I can't figure out where configure finds these to put into
`LDFLAGS` as we're not using the cc-wrapper). The end result is we get a
linker error where this new symbol can't be found at link time, even
though it's a weak import and isn't required at runtime.
Ideally we'd provide a full 10.12 SDK to `/usr/bin/clang`, but we can't
do that because even the DevSDK package we use for our 10.12 SDK doesn't
contain everything (in particular it's missing nearly all dylibs) so we
just get linker errors if we do that.
Instead we'll just do a horrible hack and provide an `-isystem` path to
a folder structure that contains only the 10.12 `sys/_types/_fd_def.h`
header. This avoids the new symbol without causing all the errors that
happen if we pull in the entire `${darwin.Libsystem}/include`.
|
| |/ /
|/| | |
|
|\ \ \
| | | |
| | | | |
R: 3.6.3 --> 4.0.0 & update packages
|
| | | |
| | | |
| | | |
| | | | |
Need the patch to backport a fix so Rstudio compiles against R 4.0.0
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Build MELPA package sets without null packages
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The current algorithm creates attributes with null values for packages
with no source in a variant of MELPA. Though will satify dependencies
they produce no files, and though a build that transitively depends on
one them will be successful, Emacs won't find them and any code
depending on them won't work.
The solution with minimal code change would have been filtering the
list of results from melpaDerivation by comparing the value against
null, but that leads to an infinite recursion.
This commit also moves legacy renames from the shared to the unstable
set, as the corresponding null value elements won't exist in the
stable set anymore.
The test used for the problem was:
$ nix-build --show-trace ./default.nix -A emacs26Packages.melpaStablePackages.findr
error: expression does not evaluate to a derivation (or a set or list of those)
The expected output, obtained with this commit is:
$ nix-build --show-trace ./default.nix -A emacs26Packages.melpaStablePackages.findr
error: attribute 'findr' in selection path 'emacs26Packages.melpaStablePackages.findr' not found
|
| | | | |
| | | | |
| | | | |
| | | | | |
It's refering to an unversioned emacswiki file with the wrong hash.
|
| | | | |
| | | | |
| | | | |
| | | | | |
It's refering to an unversioned emacswiki file with the wrong hash.
|
| | | | |
| | | | |
| | | | |
| | | | | |
It's refering to an unversioned emacswiki file with the wrong hash.
|
| | | | |
| | | | |
| | | | |
| | | | | |
It's refering to an unversioned emacswiki file with the wrong hash.
|
| | | | |
| | | | |
| | | | |
| | | | | |
It's refering to an unversioned emacswiki file with the wrong hash.
|
| | | | |
| | | | |
| | | | |
| | | | | |
It's refering to an unversioned emacswiki file with the wrong hash.
|
| | | | |
| | | | |
| | | | |
| | | | | |
It's refering to an unversioned emacswiki file with the wrong hash.
|
| | | | | |
|