Date: Thu, 14 Dec 2017 11:31:18 +0800 From: blubee blubeeme <gurenchan@gmail.com> To: Pedro Giffuni <pfg@freebsd.org> Cc: Chris H <portmaster@bsdforge.com>, FreeBSD Ports <freebsd-ports@freebsd.org>, Eugene Grosbein <eugen@grosbein.net> Subject: Re: Linux ports tutorial? WPS Office Message-ID: <CALM2mEnXpB5swZe2=UShtn8-KSbCUM97xCJpwA0YAsLnmhpzgg@mail.gmail.com> In-Reply-To: <2ca3551a-db23-1c17-2035-c67494f8f542@FreeBSD.org> References: <73820d5ad4436c73fe47d0b35a112cf5@udns.ultimatedns.net> <2ca3551a-db23-1c17-2035-c67494f8f542@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 14, 2017 at 11:17 AM, Pedro Giffuni <pfg@freebsd.org> wrote: > Hello; > > > On 13/12/2017 21:11, Chris H wrote: > >> On Wed, 13 Dec 2017 19:56:24 -0500 "Pedro Giffuni" <pfg@FreeBSD.org> sai= d >> >> On 12/10/17 14:55, Eugene Grosbein wrote: >>> > 11.12.2017 2:22, Pedro Giffuni =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >>> >> Hello guys; >>> >> >>> >> I would like to attempt a port for WPS Office (AKA Kingsoft Office): >>> >> >>> >> http://wps-community.org/ >>> >> >>> >> Are there guidelines for linux ports? I couldn't find much details i= n >>> the >>> > handbook. >>> >> >>> >> In particular, how do you handle when the pkg-plist is different for >>> i386 >>> > and amd64? >>> >> >>> >> Some ports use pkg-plist.${ARCH} but I don't know how those work. >>> > Just have "USES=3Dlinux", "USE_LINUX_RPM=3Dyes" and make these two fi= les >>> > pkg-plist.i386 and pkg-plist.amd64 >>> > and they are used automatically. Or you could duplicate a magic from >>> > /ports/Mk/Uses/linux.mk in your Makefile: >>> > >>> > PLIST?=3D ${PKGDIR}/pkg-plist.${LINUX_ARCH:S/x86_64/amd64/} >>> > >>> > For details, read Porter's Handbook: >>> > https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/ >>> > >>> >>> The handbook has no information about "USE_LINUX_RPM=3Dyes". >>> If I set that it appears the ports framework will ignore MASTER_SITES. >>> >>> Should I dig into the MK framework to see how to change the repository >>> or should I use the .tar.xz distribution instead? :(. >>> >> I'm not sure. But would having a look at the way >> emulators/linux_base-c(6|7) >> provide some clues? >> >> > Not really but I think I found something in Mk/Uses/linux.mk: > > For the case of USE_LINUX_RPM it is supposed to not do anything when > MASTER_SITES is defined but it is somewhat messy, and somehow it always > uses ${MASTER_SITE_CENTOS_LINUX}. Any port that uses RPM but not the Cent= os > repositories? > > Just a thought, and hope it helps! >> >> Thanks, I just have to keep digging :(. > > Pedro. > > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > The linux packaging is okay but I'd recommend learning how the porting process and not just wrapping up a linux binary in FreeBSD. The main reason for that is you can port your way into a corner that relies on very Linux specific stuff that there's just no solution for yet nor will there be one unless you port the entire Linux kernel to FreeBSD. If you go look at the source files and read the building and or install docs they'll give you a list of dependencies. Once you have that list dependencies, see if they are available in FreeBSD, if they are GREAT a lot of work has already been done. If not, start trying to port those dependencies to FreeBSD, once you have the full list of dependencies needed, writing a FreeBSD makefile is relatively trivial process. That would be my recommended route. Best
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALM2mEnXpB5swZe2=UShtn8-KSbCUM97xCJpwA0YAsLnmhpzgg>