Actually, we're not trying to reinvent the wheel here,
rather adapt it to suit a slightly different purpose.
Below are a few main points and reasons as to why we've created filetype:
* file does not work so well for loosely defined filetypes ( ie, vCards )
* file uses a text-based type database which can impose unwanted delays
in frequently invoked processes
* file does not have a heirachial type tree (ie, executable->MSDOS->EXE )
* file is not designed to be incorporated at a source level into existing
projects
* Simpler and broader type detection engine ( 'file' is very good at
pulling out every detail about a file, ie, the resolution of an image,
however we do not wish to seek out such fine details )
===> The following configuration options are available for filetype-0.1.3_1:
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
Actually, we're not trying to reinvent the wheel here,
rather adapt it to suit a slightly different purpose.
Below are a few main points and reasons as to why we've created filetype:
* file does not work so well for loosely defined filetypes ( ie, vCards )
* file uses a text-based type database which can impose unwanted delays
in frequently invoked processes
* file does not have a heirachial type tree (ie, executable->MSDOS->EXE )
* file is not designed to be incorporated at a source level into existing
projects
* Simpler and broader type detection engine ( 'file' is very good at
pulling out every detail about a file, ie, the resolution of an image,
however we do not wish to seek out such fine details )
WWW: http://www.pldaniels.com/filetype/
PR: ports/135087
Submitted by: ismail.yenigul at endersys.com.tr
