On 29 Dec 2012 2:03 AM, "Gerald Pfeifer" wrote:
>
> On Sat, 3 Nov 2012, David Naylor wrote:
> > # Executive Summary
> >
> > Over the past years I have been maintaining the wine-fbsd64 port (see
> > http://mediafire.com/wine_fbsd64 for more). The port itself effectively
> > does static linking (it
On Sat, 3 Nov 2012, David Naylor wrote:
> # Executive Summary
>
> Over the past years I have been maintaining the wine-fbsd64 port (see
> http://mediafire.com/wine_fbsd64 for more). The port itself effectively
> does static linking (it bundles all the libraries wine needs) with
> scripts to bo
On Sunday, 4 November 2012 13:31:46 Chris Rees wrote:
> I think this is very interesting... but I'm not 100% convinced the
> best place for this is in the ports tree. However, it would improve
> visibility for it, with a good IGNORE message.
Ideally, FreeBSD should have an automagical method of s
On Wednesday, 7 November 2012 11:45:11 Thomas Mueller wrote:
> from David Naylor :
> > Hi List,
> >
> > # Executive Summary
> >
> > Over the past years I have been maintaining the wine-fbsd64 port (see
> > http://mediafire.com/wine_fbsd64 for more). The port itself effectively
> > does static li
On Saturday, 3 November 2012 22:47:56 Jan Beich wrote:
> David Naylor writes:
> > The post-package-script (run only if WITH_PKGNG is defined):
> > - Amends the package so the arch label to 64bit
>
> WITH_PKGNG is checked too early. The port fails to fix arch on 10.0
> without the variable being
On 7 November 2012 13:57, Patrick Powell wrote:
> First, I want to thank the Wine developers for a job/life/sanity saving
> piece of code.
>
> I need both 32 and 64 versions. It would be nice if the ports had a
> wine-32 and wine-64 just to make
> life simple for us non-intensive Ports users.
First, I want to thank the Wine developers for a job/life/sanity saving
piece of code.
I need both 32 and 64 versions. It would be nice if the ports had a
wine-32 and wine-64 just to make
life simple for us non-intensive Ports users. Just a comment.
On 11/07/12 01:45, Thomas Mueller wrot
from David Naylor :
> Hi List,
> # Executive Summary
> Over the past years I have been maintaining the wine-fbsd64 port (see
> http://mediafire.com/wine_fbsd64 for more). The port itself effectively does
> static linking (it bundles all the libraries wine needs) with scripts to
> bootstrap the
Finger slip, I sent a fairly long message on this subject by a finger error
that I saw just one or two seconds later. Sorry!
Tom
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any
On 11/04/12 21:31, Chris Rees wrote:
> On 4 November 2012 11:16, Thomas Mueller wrote:
>> from David Naylor :
>>
>>> Hi List,
>>> # Executive Summary
>>> Over the past years I have been maintaining the wine-fbsd64 port (see
>>> http://mediafire.com/wine_fbsd64 for more). The port itself effective
On 4 November 2012 11:16, Thomas Mueller wrote:
> from David Naylor :
>
>> Hi List,
>
>> # Executive Summary
>
>> Over the past years I have been maintaining the wine-fbsd64 port (see
>> http://mediafire.com/wine_fbsd64 for more). The port itself effectively does
>> static linking (it bundles all
from David Naylor :
> Hi List,
> # Executive Summary
> Over the past years I have been maintaining the wine-fbsd64 port (see
> http://mediafire.com/wine_fbsd64 for more). The port itself effectively does
> static linking (it bundles all the libraries wine needs) with scripts to
> bootstrap the
David Naylor writes:
> The post-package-script (run only if WITH_PKGNG is defined):
> - Amends the package so the arch label to 64bit
WITH_PKGNG is checked too early. The port fails to fix arch on 10.0
without the variable being set explicitly in make.conf.
http://svn.freebsd.org/changeset/por
13 matches
Mail list logo
