how to install a port without install: in the Makefile

Steve Franks bahamasfranks at gmail.com
Fri Jan 23 08:08:50 PST 2009


I presume Florent's preferred method is "INSTALL_PROGRAM"?  So far,
the only doc I've found is that it exists.  So I put INSTALL_PROGRAM
$(WORKDIR)/$(PORTNAME) (portname just happens to be the name of the
executable) in the port Makefile, or what?  I've never been able to
'read' makefiles, so I'm not sure a look at ports.mk is going to cause
anything but frustration.  We've spent minutes arguing philisophy, can
I get a couple seconds of example? :)  Otherwise, PLIST_FILES looks
like it will work to me...

Best,
Steve

On Fri, Jan 23, 2009 at 7:19 AM, Florent Thoumie <flz at xbsd.org> wrote:
> On Fri, Jan 23, 2009 at 1:22 PM, Max Brazhnikov <makc at issp.ac.ru> wrote:
>> On Fri, 23 Jan 2009 06:58:02 -0600, Jeremy Messenger wrote:
>>> On Fri, 23 Jan 2009 03:47:38 -0600, Florent Thoumie <flz at xbsd.org> wrote:
>>> > On Thu, Jan 22, 2009 at 10:05 PM, Dmitry Marakasov <amdmi3 at amdmi3.ru>
>>> >
>>> > wrote:
>>> >> * Florent Thoumie (flz at xbsd.org) wrote:
>>> >>> > If it's just a single file, the preferred way is to add
>>> >>> >
>>> >>> > PLIST_FILES=    bin/program_name
>>> >>> >
>>> >>> > to the Makefile and not use pkg-plist at all.
>>> >>>
>>> >>> No, no, no.
>>> >>>
>>> >>> This is not *preferred*.
>>> >>
>>> >> Is it not? Why? There's no reason to introduce pkg-plist for just
>>> >> a single file.
>>> >
>>> > This is just an alternative way of doing it. I, for one, don't like
>>> > it. Same goes for PLIST_DIRS.
>>>
>>> +1
>>
>> You are lucky guys you have not lived in USSR. otherwise you'd surely like
>> alternative ways :)
>
> In soviet russia, alternative ways like you.
>
> I wish people remembered KISS more than TIMTOWTDI.
>
> --
> Florent Thoumie
> flz at FreeBSD.org
> FreeBSD Committer
>


More information about the freebsd-ports mailing list