Font-awesome: Create an "official" Nuget package for FontAwesome

Created on 12 Aug 2015  路  24Comments  路  Source: FortAwesome/Font-Awesome

There are many Nuget packages for FontAwesome, and they're not all kept up-to-date.

Nuget Package Name | Version | Last Update | Maintainer
------------ | ------------- | ------------- | -------------
Font.Awesome | 5.7.1 :sparkles: | 2019-02-02 | @tiesont (repo)
FontAwesome | 4.7.0 | 2016-11-04
font-awesome | 4.7.0 | 2016-11-21
FontAwesomeToolkit | 4.7.0 | 2016-11-08
hungvq.FontAwesome | 15.4.17 (assuming 4.3.0) | 2015-04-17

_(Table last updated 2019-02-02)_

Could an 'official' Nuget package be created, so that either @davegandy or @tagliala can update it whenever FortAwesome/Font-Awesome is updated?

enhancement

Most helpful comment

I've been trying to keep my NuGet packages up-to-date. I currently have 3 versions, all at 5.0.13:

All 24 comments

The following issues relate to the inability to access a Nuget package repo:

  • #569 [..] include .less files in Nuget
  • #6067 Push 4.3.0 to Nuget
  • #7051 Nuget version
  • #7190 Nuget package update

This issue has been raised previously in 2012, as #313. @davegandy explained then that this couldn't happen because it required access to a .exe

Is this still the case? Are there alternatives that don't require an .exe? Since I assume once the package repo is initially set up, the only difference between revisions is in the .css and .less files?

@BenJenkinson did you try to contact the project owner JiveCode?

@tagliala The "FontAwesome" Nuget package is powered by the JustLikeIcarus/Font-Awesome-NuGet GitHub repo. There's an outstanding issue there to upgrade it to 4.3.0, that I left another comment on.

+1 - I'd love to see an "official" package - I was using the FontAwesome package (4.2), but I couldn't use any of the new icons shown on http://fontawesome.io/whats-new/, so now I've switched to the (far-less-popular, but up-to-date!) Font.Awesome package (4.4).

+1

+1 - Would love a Font Awesome package that always kept the most recent version installed.

+1 please

come on guys, not so difficult, and a great reach into .net developers!
great package anyway! =)

with the update to the version 4.7 the situation doesn't change! :(

+1! I'd love to have this to assist with .NET development since npm just isn't as easy.

I've been trying to keep my NuGet packages up-to-date. I currently have 3 versions, all at 5.0.13:

@tiesont : Thank you! Back in Feb., I think your packages weren't as up to date and I know how hard it is to keep up to date. So, again; thank you!

@tiesont @davegandy Hi, I appreciate the creation of the NuGet packages and I am using them. Can we plan to update them to the latest version of Font.Awesome? I'd like to gain access to the new icons. Thanks!

@mseminatore My packages are not officially supported by Font Awesome, so posting here is probably not the best idea. I received the notice from NuGet, so please stick to that until I have time to setup a repo for my packages.

I've created a repo for my packages, https://github.com/tiesont/Font.Awesome.Packages - I'll update the packages with the next release to point there, rather than to fontawesome.com.

@tiesont I've asked him to contact you or to mention you here.

It's fine for me, and thanks for your efforts in creating a NuGet package.

@mseminatore please do not mention Dave and refer to https://github.com/tiesont/Font.Awesome.Packages for the moment if you have issues with this package. Again, it isn't an official package

@tagliala Thank you and sorry for the confusion. @tiesont Understood, that is why I sent the message through NuGet. Love what you all are doing, keep up the great work! If there is something I can do to help let me know.

@tiesont Thank you!

Added packages for 5.6.1 and 5.6.3 (sorry, missed the initial release again). Enjoy.

@tiesont thanks! And, if you can, please remove the 5.6.1 release at all (is there something like gem yank) ?

@tagliala There isn't a way to truly remove a version, but I can unlist it.

@tiesont yes, please unlist it

@tagliala Done. Will take a bit for NuGet to reindex the packages, but after that the 5.6.1 versions will not be installable.

Updated my packages to 5.7.1.

@tagliala should I keep updating here, or should I just assume anyone who's using my NuGet packages can figure this out on their own?

@tiesont feel free to skip comments here, maybe someone will comment only when a release is missing

As always, thanks for keeping this package up-to-date

Was this page helpful?
0 / 5 - 0 ratings

Related issues

sezeresen picture sezeresen  路  3Comments

AndersDK12 picture AndersDK12  路  3Comments

huuphat picture huuphat  路  3Comments

brystfire08 picture brystfire08  路  3Comments

tdolph picture tdolph  路  3Comments