Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

35

Downloads of v 2.10.2:

35

Last Update:

09 Sep 2020

Package Maintainer(s):

Software Author(s):

  • FreeType Team.

Tags:

freetype dll

FreeType (DLL)

Downloads:

35

Downloads of v 2.10.2:

35

Maintainer(s):

Software Author(s):

  • FreeType Team.

Tags:

freetype dll

FreeType (DLL)

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Failed

Details

Scan Testing Successful:

No detections found in any package files

Details
WARNING

This package was rejected on 16 Oct 2020. The reviewer chocolatey-ops has listed the following reason(s):

chtof (maintainer) on 09 Sep 2020 20:29:38 +00:00:

User 'chtof' (maintainer) submitted package.

chocolatey-ops (reviewer) on 09 Sep 2020 21:02:38 +00:00:

freetype has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • Description should be sufficient to explain the software. Please fill in the description with more information about the software. Feel free to use use markdown. More...
Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 09 Sep 2020 22:40:46 +00:00:

freetype has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/ed03bdf30e77569612bb3d18e11d9d5e for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

chtof (maintainer) on 10 Sep 2020 06:54:52 +00:00:

2020-09-06 07:07:02,168 2296 [INFO ] -
2020-09-06 07:07:02,168 2296 [WARN ] - Packages requiring reboot:
2020-09-06 07:07:02,183 2296 [WARN ] - - kb2919355 (exit code 3010)
2020-09-06 07:07:02,183 2296 [WARN ] -

Could you exempt this package?

gep13 (reviewer) on 11 Sep 2020 07:08:30 +00:00:

What is the link between:

https://www.freetype.org/

and

https://github.com/ubawurinna/freetype-windows-binaries

Copying the files directly into the system32 folder, is that really what needs to happen here? Is this documented somewhere?

chocolatey-ops (reviewer) on 01 Oct 2020 07:09:45 +00:00:

We've found freetype v2.10.2 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:

  • Log in to the site and respond to the review comments.
  • Resubmit fixes for this version.
  • If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

chocolatey-ops (reviewer) on 16 Oct 2020 07:14:43 +00:00:

Unfortunately there has not been progress to move freetype v2.10.2 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.

Status Change - Changed status of package from 'submitted' to 'rejected'.

Description

Windows DLLs of FreeType.


legal\LICENSE.txt

From: https://raw.githubusercontent.com/ubawurinna/freetype-windows-binaries/master/LICENSE.TXT

LICENSE


The  FreeType 2  font  engine is  copyrighted  work and  cannot be  used
legally  without a  software license.   In  order to  make this  project
usable  to a vast  majority of  developers, we  distribute it  under two
mutually exclusive open-source licenses.

This means  that *you* must choose  *one* of the  two licenses described
below, then obey  all its terms and conditions when  using FreeType 2 in
any of your projects or products.

  - The FreeType License, found in  the file `FTL.TXT', which is similar
    to the original BSD license *with* an advertising clause that forces
    you  to  explicitly cite  the  FreeType  project  in your  product's
    documentation.  All  details are in the license  file.  This license
    is  suited  to products  which  don't  use  the GNU  General  Public
    License.

    Note that  this license  is  compatible  to the  GNU General  Public
    License version 3, but not version 2.

  - The GNU General Public License version 2, found in  `GPLv2.TXT' (any
    later version can be used  also), for programs which already use the
    GPL.  Note  that the  FTL is  incompatible  with  GPLv2 due  to  its
    advertisement clause.

The contributed BDF and PCF drivers  come with a license similar to that
of the X Window System.  It is compatible to the above two licenses (see
file src/bdf/README and  src/pcf/README).  The same holds  for the files
`fthash.c' and  `fthash.h'; their  code was  part of  the BDF  driver in
earlier FreeType versions.

The gzip module uses the zlib license (see src/gzip/zlib.h) which too is
compatible to the above two licenses.

The MD5 checksum support (only used for debugging in development builds)
is in the public domain.


--- end of LICENSE.TXT ---
legal\VERIFICATION.txt
VERIFICATION
 
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
 
Package can be verified like this:
 
1. Download:
 
   x32: https://raw.githubusercontent.com/ubawurinna/freetype-windows-binaries/master/win32/freetype.dll
   x64: https://raw.githubusercontent.com/ubawurinna/freetype-windows-binaries/master/win64/freetype.dll
  
2. You can use one of the following methods to obtain the SHA256 checksum:
   - Use powershell function 'Get-FileHash'
   - Use Chocolatey utility 'checksum.exe'
 
   checksum type: sha256
   checksum32: F310B76AC5B1231705326DCB18C1D61FAF44C6E066563029586E1B91FE04EF03
   checksum64: C3E80C1BD7C8E2797EA543B8E9AC7B8D1989AD3F87F371CE1783D1907D3D0FF5
 
File 'LICENSE.txt' is obtained from:
   https://raw.githubusercontent.com/ubawurinna/freetype-windows-binaries/master/LICENSE.TXT
tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

Copy-Item -Force "$toolsDir\win$(Get-OSArchitectureWidth)\freetype.dll" $env:SystemRoot\system32
tools\chocolateyuninstall.ps1
$ErrorActionPreference = 'Stop';
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

Remove-Item -Force "$env:SystemRoot\system32\freetype.dll"
tools\win32\freetype.dll
md5: 3ED99826865671EAA0082C85647631DD | sha1: 6FA0DF400FC4C415EC97870A93273DA011154453 | sha256: F310B76AC5B1231705326DCB18C1D61FAF44C6E066563029586E1B91FE04EF03 | sha512: 664F0D3159FF39420A957B232A2808CE16EBA7B6D5AC31D3BF9F78A1828BBAECB2C9331FCF9106E62AFCC5FE46E3E0580FA53F8C42F6FEAB113F8365F2FBAEF0
tools\win64\freetype.dll
md5: 39F957C73D78A215C074B480570970CD | sha1: 7B675334DEDCBA07FBCA18DA59EF570BD0079BC0 | sha256: C3E80C1BD7C8E2797EA543B8E9AC7B8D1989AD3F87F371CE1783D1907D3D0FF5 | sha512: 3722EE6090455C446CA1425BBCA27CF4BDCFB7C905E5223916756C62F3AB25BD9046429D9201DEAC60A40D02F9DB3F67ECE62FC56FB7E73C07EF2710FE51DC0C

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status

Discussion for the FreeType (DLL) Package

Ground Rules:

  • This discussion is only about FreeType (DLL) and the FreeType (DLL) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or FreeType (DLL), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus