Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 30 Sep 2012 20:15:00 +0200
From:      David Naylor <naylor.b.david@gmail.com>
To:        Chuck Burns <break19@gmail.com>
Cc:        freebsd-emulation@freebsd.org
Subject:   Re: Wine-fbsd64 updated to 1.5.13 (32bit Wine for 64bit FreeBSD)
Message-ID:  <201209302015.06716.naylor.b.david@gmail.com>
In-Reply-To: <50687DFD.4020304@gmail.com>
References:  <201209242229.36933.naylor.b.david@gmail.com> <201209301834.31015.naylor.b.david@gmail.com> <50687DFD.4020304@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart10794935.rnuDr4su1Z
Content-Type: multipart/mixed;
  boundary="Boundary-01=_kwIaQGc+4H27DVD"
Content-Transfer-Encoding: 7bit


--Boundary-01=_kwIaQGc+4H27DVD
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Sunday, 30 September 2012 19:14:37 Chuck Burns wrote:
> On 09/30/2012 11:34 AM, David Naylor wrote:
> > On Sunday, 30 September 2012 16:22:30 Chuck Burns wrote:
> >> On 09/30/2012 09:06 AM, David Naylor wrote:
> >>> The current pkg format can be installed along side a pkgng
> >>> installation (the nvidia patching will detect the pkgng packages). Has
> >>> this not worked on your setup?
> >>=20
> >> Yes, this works, I was hoping to be as "native" as possible. :)
> >=20
> > Doing so will increase my workload by 33% and I'm not willing to devote
> > extra resources given that it currently works anyway.
> >=20
> > However, the usage of the FreeBSD-8 packages are low, so I may drop
> > support for them and reconsider supporting pkgng for FreeBSD 9.  It
> > would also provide an interesting barometer for adoption of pkgng (I
> > myself use it, except for wine packages, on FreeBSD-9).
> >=20
> > Regards
>=20
> How do you build this, anyway? I would love to be able to "cut out the
> middle man" so to speak.  I know the general idea is: build it in a
> 32bit jail.  But do you do it with a script? or just manually build the
> packages?

Since you asked ;-) ...

I have a custom Makefile that manages my source files (for FreeBSD and Port=
s)=20
and a script file that uses the Makefile to build the wine packages.  The=20
actual commands that I use are:
# make -sj8 update ports
# sh wine-fbsd.sh
# env FBSD=3Dfreebsd8 sh wine-fbsd.sh
# env FBSD=3Dfreebsd10 sh wine-fbsd.sh

The script file is straight forward and the calls to `make -f /root/Makefil=
e -
j8 pkg-env ...` can be simply replaced with:
# make -C /usr/src -sj8 world DESTDIR=3D$SCRATCHPAD
to get the same effect.  Note: /home/DragonSA/ports/wine-fbsd64.diff is the=
=20
diff from mediafire. =20

The Makefile is very specific to my setup, where I have a server that mirro=
rs=20
(using csup) FreeBSD 8, 9 and 10, and Ports, and I have /usr/ports and=20
/usr/src as a symlink to /home/ports and /home/freebsd9/src respectively.  =
I=20
include it for completeness, if not for its actual usefulness. =20

It shouldn't be difficult to create a script that is more general (maybe us=
ing=20
portsnap [and svn export?] as cvs is being depreciated).  If you do I will=
=20
happily upload it to mediafire ;-)

Regards

--Boundary-01=_kwIaQGc+4H27DVD--

--nextPart10794935.rnuDr4su1Z
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iEYEABECAAYFAlBojCoACgkQUaaFgP9pFrKRrwCfd/rlnkm8YjyTIIpaATTN/aq4
zuwAmwZUR2N7cc756mBRur6Nk1lOq0bQ
=Lzek
-----END PGP SIGNATURE-----

--nextPart10794935.rnuDr4su1Z--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201209302015.06716.naylor.b.david>