Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 20 May 2015 14:47:08 -0500 (CDT)
From:      "Valeri Galtsev" <galtsev@kicp.uchicago.edu>
To:        "Polytropon" <freebsd@edvax.de>
Cc:        "John Johnstone" <jjohnstone@tridentusa.com>, "Jeffry Killen" <jekillen@prodigy.net>, freebsd-questions@freebsd.org
Subject:   Re: freetype in ports?
Message-ID:  <60123.128.135.70.2.1432151228.squirrel@cosmo.uchicago.edu>
In-Reply-To: <20150520213003.81724640.freebsd@edvax.de>
References:  <A59CC0EB-8F5D-47DF-8800-BC433DE1939C@prodigy.net> <20150520200456.49f6ee31.freebsd@edvax.de> <50466.128.135.70.2.1432145863.squirrel@cosmo.uchicago.edu> <555CDD7B.5060102@tridentusa.com> <20150520213003.81724640.freebsd@edvax.de>

next in thread | previous in thread | raw e-mail | index | archive | help

On Wed, May 20, 2015 2:30 pm, Polytropon wrote:
> On Wed, 20 May 2015 15:16:11 -0400, John Johnstone wrote:
>> On 5/20/15 2:17 PM, Valeri Galtsev wrote:
>> >
>> > On Wed, May 20, 2015 1:04 pm, Polytropon wrote:
>> >> On Wed, 20 May 2015 10:36:17 -0700, Jeffry Killen wrote:
>> >>> Hello;
>> >>>
>> >>> I want to add freetype to system so I can build php5.6x with GD,
>> with
>> >>> freetype
>> >>> ttf font support.
>> >>>
>> >>> I did
>> >>> find /usr/ports *freetype* and no match came up
>> >>>
>> >>> same with
>> >>> find /usr/ports FreeType2 and no match came up
>> >
>> > I would use unix find comand as follows:
>> >
>> > find /usr/ports -name \*freetype\*
>> >
>> > But the suggestion by Mr. Polytropon below is much better (as it
>> doesn't
>> > care about case to the contrary to find command above...
>>
>> How about -iname?
>
> Also possible, but it will find _any_ file (or even directory)
> which contains the search pattern. This may be a lot, whereas
> the _question_ you want answered is: Where does <something> live
> within the ports tree? For this question, I think using "make search"
> is the more convenient method, especially because of its output:
> Whereas find will list (correctly) found files and directories,
> "make search" will give you the port directory and additional
> information. In my opinion, this is easier to read.
>
> By the way, you can turn
>
> 	# cd /usr/src
> 	# make search name="freetype"
>
> into
>
> 	# make -C /usr/ports search name="freetype"
>

Thanks Mr. Polytropon! The moment I saw your suggestion I told myself I
will never use unix find command when I need something related to ports
make search name="[whatever]" in /usr/ports makes much more sense. You
learn something every day!

Valeri

> and create a shell alias, if you need this more often. :-)
>
> Even better: If you intend to search for some word(s) in the
> ports description, use key= instead of name= to search for
> keywords.
>
> Finally allow me to repeat "man 7 ports" which lists several
> other search "queries".
>
>
>
> --
> Polytropon
> Magdeburg, Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe, Mousa, ...
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe@freebsd.org"
>


++++++++++++++++++++++++++++++++++++++++
Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247
++++++++++++++++++++++++++++++++++++++++



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?60123.128.135.70.2.1432151228.squirrel>