zurb-foundation 5 came out yesterday - is there an updated gem file? - zurb-foundation

Trying to update the ruby zurb-foundation gem today. I thought foundation also got an updated gem after releasing version 5. Is there an updated version or is version 4.3.2 the latest gem in the repository?
I tryed:
gem search --remote --al zurb-foundation
result was:
zurb-foundation (4.3.2, 4.3.1, 4.3.0, 4.2.3, 4.2.2, 4.2.1, 4.2.0, 4.
4.1.2, 4.1.1, 4.0.9, 4.0.8, 4.0.7, 4.0.5, 4.0.4, 4.0.3, 4.0.2, 4.0.1
.5, 3.2.4, 3.2.3, 3.2.2, 3.2.0, 3.1.1, 3.1.0, 3.0.9, 3.0.8, 3.0.7, 3
3.0.4, 3.0.3, 2.2.1.2, 2.2.1.1, 2.2.1.0, 2.2.0.2, 2.2.0.1, 2.1.5.1,
1.4.3, 2.1.4.2, 2.1.4.1, 2.1.4, 2.1.3.1, 2.1.3, 2.1.2, 2.1.0, 2.0.3.
2.0.3.1, 2.0.2, 2.0.1, 2.0.0, 1.0.0, 0.0.5)
ZURB-foundation (2.2.1.4, 2.2.1.3, 2.2.1.2, 2.2.1.1, 2.2.1, 2.2.0.1,
2, 2.1.5.1, 2.1.5, 2.1.4.1, 2.1.4, 2.1.3.3, 2.1.3.2, 2.1.3.1, 2.1.3)

They've released the gem under a different name, it's just called foundation now instead of foundation-zurb.
Installation instructions can be found at http://foundation.zurb.com/docs/sass.html.

I found the same thing. It looks like they use bower now. I find its rather annoying to have to install nodejs, git and bower just to get the latest release.
Edit:
More here: http://foundation.zurb.com/docs/sass.html

Related

How do I get VS 2017 to install the dependencies for packages that I am trying to install?

I was following a Lynda tutorial that was showing how to add versioning to my APIs. It told me to install the NuGet package Microsoft.AspNetCore.Mvc.Versioning. I tried that and it gave me an error because it needed Microsoft.AspNetCore.Mvc.Core. So I tried to install that package, and, again, another error because it needed another package.
So I started googling for a way to make VS 2017 pull in dependencies with NuGet installation. None of the answers that I found were helpful. I’ve tried managing as packageReference and packages.config. “Allow format selection on first package install” is unchecked. And so on.
So I decided to just power through and add all the dependencies manually. I had to install 29 packages. It took me over half an hour, not including time spent chasing the cat up and down the stairs screaming at the top of my lungs.
Is there some switch I forgot to flip, or some options I didn't add, or does Microsoft really think we might want the option to install a package without installing its dependencies?
How do I get VS 2017 to install the dependencies for packages that I am trying to install?
I have reproduced this issue on my side. This is the correct behavior for nuget. That because the package which you want to install have a indirect dependency Microsoft.AspNetCore.Authentication.Abstractions (>= 2.2.0).
Note: (Version need >= 2.2.0).
However, the default package for the .net core API project also have same indirect dependency Microsoft.AspNetCore.Authentication.Abstractions (>= 2.1.1 && < 2.2.0) with version limit (>= 2.1.1 && < 2.2.0).
Note: version limit (>= 2.1.1 && < 2.2.0).
It conflict with dependency of package Microsoft.AspNetCore.Mvc.Versioning. That the reason why nuget not install the dependencies for package.
To resolve this issue, we just need to update the target framework (Right click project->Properties->Target Framework) from .NET Core 2.1 to .NET Core 2.2 for your .net core API project.
If you do not have the version 2.2.0, please download it from here and install it:
.NET SDKs for Visual Studio
After update the target framework to 2.2, the default package Microsoft.AspNetCore.App will be update to Microsoft.AspNetCore.App 2.2.0, which dependency update to Microsoft.AspNetCore.Authentication.Abstractions(>= 2.2.0 && < 2.3.0). So it compatible with the dependencies of the package Microsoft.AspNetCore.Mvc.Versioning 3.1.1.
Now I can install the package Microsoft.AspNetCore.Mvc.Versioning 3.1.1 with its dependency.
Hope this helps.

List all opam package versions compatible with a given OCaml compiler

opam info package has a field available-versions, which lists all versions of a given package that are available for at least one OCaml version.
What is much more useful to me, in everyday usage, is the list of package versions that are available for my current OCaml version.
For instance, if I am currently on OCaml 4.05.0, and I run opam info merlin, I get:
available-versions: 1.3, 1.3.1, 1.3.1-trunk, 1.4, 1.4.1, 1.5, 1.6, 1.7,
1.7.1, 2.0.0, 2.1.0, 2.1.1, 2.1.2, 2.2, 2.3, 2.3.1, 2.5.0, 2.5.1, 2.5.2,
2.5.3, 2.5.4, 2.5.5, 3.0.0, 3.0.1, 3.0.2, 3.0.3
But if I try opam install merlin.1.3, it fails:
[ERROR] merlin.1.3 is not available because your system doesn't comply
with ocaml-version > "4.00.1" & ocaml-version < "4.02.0".
Note that opam list only outputs a single line (installed version, or -- if not installed), so it also does not allow knowing which versions are installable.
Is there a way to directly obtain all package versions that are actually available (for my current compiler), other than by trying to install each one of them?
I'm going to use opam 2.0. You have two options for this purpose:
opam list --available merlin will list things only by looking at the switch, the environment and the merlin package itself. This option should be available in opam 1.3.
opam list --installable merlin will actually run the solver to check if things are ok. This means dealing with the dependencies, in particular. I think this option is new to 2.0.
Finally, the option --all-versions allows you to force opam to list all the versions for each packages.

OpenSuse: Cannot start Omnisharp because Mono version >=3.10.0 is required

Im running Visual Studio Code on OpenSuse 13.2 and get "Cannot start Omnisharp because Mono version >=3.10.0 is required". I have reinstalled mono-complete and mono-devel.
OpenSuse 13.2 repositories contains mono version 3.8.0. To install newer version, firstly uninstall current version of mono and then visit this page and click "1-click Install mono-complete" to install latest version of mono (currently version 4.0.2)

Rails 4 bundle update error with gem atomic 1.1.16

Rails bundle update keeps failing on processing atomic gem v 1.1.16. Have searched the web back and forth for solution. Checked gcc --version:
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include- dir=/usr/include/c++/4.2.1
Apple LLVM version 5.1 (clang-503.0.38) (based on LLVM 3.4svn)
Target: x86_64-apple-darwin13.1.0
Thread model: posix
Installed xcode command lines, ran gem system updates, uninstalled previous atomic versions and tried to reinstall 1.1.16. Same result:
...
clang: error: unknown argument: '-multiply_definedsuppress' [-Wunused-command-line-argument-hard-error-in-future]
clang: note: this will be a hard error (cannot be downgraded to a warning) in the future
make: *** [atomic_reference.bundle] Error 1
make failed, exit code 2
Does anybody have a hint? Thanks in advance.
UPDATE
These are the nearest to solution I have found so far from google groups and github.
Seems to be a yet unsolved issue of osx Mavericks and/or Xcode.
But the modified bundle install hint at least gets it to run complete.
I wonder if it's a problem with the version of Rails and Ruby you are using.
I'm using Rails 4.0.2 and RVM 1.25.16 for management of ruby versions (currently have 2.0.0p247 and 2.0.0-p353). I'm on OS X Mavericks, Version 10.9.1.
I originally installed ruby 2.0.0p247, and this is still the default for terminal. But I later installed with RVM ruby 2.0.0p353. I was also getting errors with install of the atomic gem, even for a new project. But when I switch to the latest version of ruby with rvm (rvm ruby-2.0.0-p353), everything now installs properly. I'm not sure what's going on or why that fixed it. I hope this helps.

handlebar precompile version error in Ember rc5

I'm upgrading to Ember rc5 from rc3, but I'm getting the following error:
Uncaught Template was precompiled with an older version of Handlebars than the current runtime. Please update your precompiler to a newer version (>= 1.0.0-rc.4) or downgrade your runtime to an older version (== 1.0.0-rc.3)
Here are the relevant lines in my gemfile, taken straight from the ember-rails README (except pulling the gem from git... it gives the same error whether I include that or not)
gem 'ember-rails', git: 'https://github.com/emberjs/ember-rails.git'
gem 'ember-source', '1.0.0.rc5'
gem 'handlebars-source', '1.0.0.rc4'
I'm using rails 3.2
I know this problem has come up before, but none of the solutions I've found have made a difference. Things that haven't worked:
deleting precompiled assets
rake tmp:clear
making sure my javascrcipt load order is jquery, then handlebars, then ember
restarting the server
threatening the compiler
giving up hope and watching Buffy reruns
trying all of those in conjunction, in every imaginable order
Simple and definitive answers are best, of course, but I'd also be glad for hints on what I can study to figure this out on my own. I don't know where to start.
For now, ensure your Gemfile is using the edge version:
gem 'ember-rails', :git => 'git://github.com/emberjs/ember-rails.git'
gem 'ember-source', '1.0.0.rc5'
gem 'handlebars-source', '1.0.0.rc4'
A new version of the gem should be released to resolve the issue soon. This fixed the problem for me.