Re: Linux ports tutorial? WPS Office

[Eugene Grosbein]

11.12.2017 2:22, Pedro Giffuni пишет:
> 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 in 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=linux", "USE_LINUX_RPM=yes" and make these two files 
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?= ${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/

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Linux ports tutorial? WPS Office

[blubee blubeeme]

The first step would be to take a look at the source code the .tar file and
see a list of dependencies, then check to see if those dependencies already
have ports in FreeBSD ports tree.

What are the dependencies described in the docs for that office suite?

On Mon, Dec 11, 2017 at 3:55 AM, Eugene Grosbein  wrote:

> 11.12.2017 2:22, Pedro Giffuni пишет:
> > 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 in
> 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=linux", "USE_LINUX_RPM=yes" and make these two files
> 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?= ${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/
>
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Linux ports tutorial? WPS Office

[Pedro Giffuni]

On 12/10/17 14:55, Eugene Grosbein wrote:

11.12.2017 2:22, Pedro Giffuni пишет:

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 in 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=linux", "USE_LINUX_RPM=yes" and make these two files 
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?= ${PKGDIR}/pkg-plist.${LINUX_ARCH:S/x86_64/amd64/}

Thanks, this is a good starting point.

For details, read Porter's Handbook: 
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/


Pedro.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Linux ports tutorial? WPS Office

[Pedro Giffuni]

On 12/10/17 14:55, Eugene Grosbein wrote:

11.12.2017 2:22, Pedro Giffuni пишет:

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 in 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=linux", "USE_LINUX_RPM=yes" and make these two files 
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?= ${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=yes".
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? :(.


Pedro.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Linux ports tutorial? WPS Office

[Chris H]

On Wed, 13 Dec 2017 19:56:24 -0500 "Pedro Giffuni"  said


On 12/10/17 14:55, Eugene Grosbein wrote:
> 11.12.2017 2:22, Pedro Giffuni пишет:
>> 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 in 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=linux", "USE_LINUX_RPM=yes" and make these two files
> 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?= ${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=yes".
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?

Just a thought, and hope it helps!

--Chris


Pedro.



___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Linux ports tutorial? WPS Office

[Pedro Giffuni]

Hello;


On 13/12/2017 21:11, Chris H wrote:

On Wed, 13 Dec 2017 19:56:24 -0500 "Pedro Giffuni"  said


On 12/10/17 14:55, Eugene Grosbein wrote:
> 11.12.2017 2:22, Pedro Giffuni пишет:
>> 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 
in 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=linux", "USE_LINUX_RPM=yes" and make these two files
> 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?= ${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=yes".
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 
Centos 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-unsubscr...@freebsd.org"

Re: Linux ports tutorial? WPS Office

[blubee blubeeme]

On Thu, Dec 14, 2017 at 11:17 AM, Pedro Giffuni  wrote:

> Hello;
>
>
> On 13/12/2017 21:11, Chris H wrote:
>
>> On Wed, 13 Dec 2017 19:56:24 -0500 "Pedro Giffuni"  said
>>
>> On 12/10/17 14:55, Eugene Grosbein wrote:
>>> > 11.12.2017 2:22, Pedro Giffuni пишет:
>>> >> 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 in
>>> 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=linux", "USE_LINUX_RPM=yes" and make these two files
>>> > 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?= ${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=yes".
>>> 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 Centos
> 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-unsubscr...@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
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Linux ports tutorial? WPS Office

[Pedro Giffuni]

On 12/13/17 22:31, blubee blubeeme wrote:



On Thu, Dec 14, 2017 at 11:17 AM, Pedro Giffuni > wrote:


Hello;


On 13/12/2017 21:11, Chris H wrote:

On Wed, 13 Dec 2017 19:56:24 -0500 "Pedro Giffuni"
 said

On 12/10/17 14:55, Eugene Grosbein wrote:
> 11.12.2017 2:22, Pedro Giffuni пишет:
>> 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 in 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=linux", "USE_LINUX_RPM=yes" and make
these two files
> 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?= ${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=yes".
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 Centos 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-unsubscr...@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.




Well ... of course if I had the source code I would not be dealing RPMs 
for the linuxulator.


Software can be free but not include source code.  It can still be 
desirable for 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.




Which is why we have a linuxulator.

Pedro.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Linux ports tutorial? WPS Office

[blubee blubeeme]

On Thu, Dec 14, 2017, 22:15 Pedro Giffuni  wrote:

>
>
> On 12/13/17 22:31, blubee blubeeme wrote:
>
>
>
> On Thu, Dec 14, 2017 at 11:17 AM, Pedro Giffuni  wrote:
>
>> Hello;
>>
>>
>> On 13/12/2017 21:11, Chris H wrote:
>>
>>> On Wed, 13 Dec 2017 19:56:24 -0500 "Pedro Giffuni" 
>>>  said
>>>
>>> On 12/10/17 14:55, Eugene Grosbein wrote:
 > 11.12.2017 2:22, Pedro Giffuni пишет:
 >> 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
 in 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=linux", "USE_LINUX_RPM=yes" and make these two files
 > 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?= ${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=yes".
 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 Centos
>> 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-unsubscr...@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.
>
>
> Well ... of course if I had the source code I would not be dealing RPMs
> for the linuxulator.
>
> Software can be free but not include source code.  It can still be
> desirable for 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.
>
>
> Which is why we have a linuxulator.
>
>
> Pedro.
>
What's in these tar.gz files here: http://wps-community.org/downloads
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Linux ports tutorial? WPS Office

[Kurt Jaeger]

Hi!

> > Well ... of course if I had the source code I would not be dealing RPMs
> > for the linuxulator.
[...]

> What's in these tar.gz files here: http://wps-community.org/downloads

I've downloaded 

http://kdl1.cache.wps.com/ksodl/download/linux/a21//wps-office_10.1.0.5707~a21_x86_64.tar.xz

and found binaries for linux, but no source code.

-- 
p...@opsec.eu+49 171 3101372 3 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Linux ports tutorial? WPS Office

[Pedro Giffuni]

On 12/14/17 10:57, blubee blubeeme wrote:




On Thu, Dec 14, 2017, 22:15 Pedro Giffuni > wrote:




On 12/13/17 22:31, blubee blubeeme wrote:



On Thu, Dec 14, 2017 at 11:17 AM, Pedro Giffuni mailto:p...@freebsd.org>> wrote:

Hello;


On 13/12/2017 21:11, Chris H wrote:

On Wed, 13 Dec 2017 19:56:24 -0500 "Pedro Giffuni"
  said

On 12/10/17 14:55, Eugene Grosbein wrote:
> 11.12.2017 2:22, Pedro Giffuni пишет:
>> 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 in 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=linux", "USE_LINUX_RPM=yes" and
make these two files
> 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?=
${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=yes".
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 Centos 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-unsubscr...@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.



Well ... of course if I had the source code I would not be dealing
RPMs for the linuxulator.

Software can be free but not include source code.  It can still be
desirable for 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.



Which is why we have a linuxulator.


Pedro.

What's in these tar.gz files here: http://wps-community.org/downloads


binaries:

libauth.so  libtiff.so.4
libavcodec.so   libtiff.so.4.3.4
libavcodec.so.57    libtxtrw.so
libavcodec.so.57.24.102 libwordconvert.so
libavformat.so  libwordml12w.so
libavformat.so.57   libwppcore.so
libavformat.so.57.25.100    libwpsdocxrw.so
libavutil.so    libwpshtmlrw.so
libavutil.so.55 libwpsio.so
libavutil.so.55.17.103  libwpstablestyle.so
libc++.so   libwpswordtool.so
libc++.so.1 libwpsxmlrw.so
libc++.so.1.0   libxercesc3.so
libc++abi.so    libxlsxrw.so
libc++abi.so.1  mui
libc++abi.so.1.0    qt
libdap.so   qt.conf
libdocreader.so res
libdocwriter.so skins
libethtmlrw2.so thirdpartylegalnotices.txt
libethtmrw.so   transerr
libetsolver.so  wpp
libetxmlrw.so   wps
...
___
fre

Re: Linux ports tutorial? WPS Office

[Chris H]

On Thu, 14 Dec 2017 09:15:35 -0500 "Pedro Giffuni"  said

On 12/13/17 22:31, blubee blubeeme wrote:
On Thu, Dec 14, 2017 at 11:17 AM, Pedro Giffuni > wrote:


Hello;
On 13/12/2017 21:11, Chris H wrote:
On Wed, 13 Dec 2017 19:56:24 -0500 "Pedro Giffuni"
 said

On 12/10/17 14:55, Eugene Grosbein wrote:

11.12.2017 2:22, Pedro Giffuni пишет:

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 in 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=linux", "USE_LINUX_RPM=yes" and make

these two files

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?= ${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=yes".
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 Centos repositories?

Just a thought, and hope it helps!

Thanks, I just have to keep digging :(.

Pedro.

The linux packaging is okay but I'd recommend learning how the porting 
process and not just wrapping up a linux binary in FreeBSD.




Well ... of course if I had the source code I would not be dealing RPMs 
for the linuxulator.


Software can be free but not include source code.  It can still be 
desirable for 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.




Which is why we have a linuxulator.

OK Pedro, just so I know I understand your intentions correctly;
You need a way to unpack all the .rpm's, and separate them by
$arch -- 32bit -vs- 64bit, so that you can create the correct pkg-plist(s)
for each of them. Is that correct?

I'll await your response before a solution for that.

--Chris


Pedro.



___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Linux ports tutorial? WPS Office

[Chris H]

On Thu, 14 Dec 2017 17:59:34 -0500 "Pedro Giffuni"  said


On 12/14/17 17:07, Chris H wrote:
> On Thu, 14 Dec 2017 09:15:35 -0500 "Pedro Giffuni"  said
>> On 12/13/17 22:31, blubee blubeeme wrote:
>>> On Thu, Dec 14, 2017 at 11:17 AM, Pedro Giffuni >>> > wrote:

>>>
>>> Hello;
>>> On 13/12/2017 21:11, Chris H wrote:
>>> On Wed, 13 Dec 2017 19:56:24 -0500 "Pedro Giffuni"
>>>  said
>>>
>>> On 12/10/17 14:55, Eugene Grosbein wrote:
 11.12.2017 2:22, Pedro Giffuni пишет:
> 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 in 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=linux", "USE_LINUX_RPM=yes" and make
>>> these two files
 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?= ${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=yes".
>>> 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 Centos repositories?
>>>
>>>     Just a thought, and hope it helps!
>>>
>>> Thanks, I just have to keep digging :(.
>>>
>>> Pedro.
>>>
>>> The linux packaging is okay but I'd recommend learning how the 
>>> porting process and not just wrapping up a linux binary in FreeBSD.

>>>
>>
>> Well ... of course if I had the source code I would not be dealing 
>> RPMs for the linuxulator.

>>
>> Software can be free but not include source code.  It can still be 
>> desirable for 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.

>>>
>>
>> Which is why we have a linuxulator.
> OK Pedro, just so I know I understand your intentions correctly;
> You need a way to unpack all the .rpm's, and separate them by
> $arch -- 32bit -vs- 64bit, so that you can create the correct 
> pkg-plist(s)

> for each of them. Is that correct?
>
> I'll await your response before a solution for that.
>

I did that already, thanks.
The trick was defining DISTFILES_amd64, DISTFILES_i386 and SRC_DISTFILES.

Now the problem is that our RPM support doesn't expect to find files 
installed in usr/bin and share.


At some point I decided it was better to use the .tar.xz distribution 
but that uses version of glibc and libpng that don't match either of the 
centos distributions we carry. So I am back to RPMs.

Can't you just *omit* those, and use those already supplied by FreeBSD?
Maybe those in the linux_base ports, via (run|make)depends?

just a thought. :-)

--Chris



Cheers,

Pedro.



___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Linux ports tutorial? WPS Office

[Pedro Giffuni]

On 12/14/17 17:07, Chris H wrote:

On Thu, 14 Dec 2017 09:15:35 -0500 "Pedro Giffuni"  said

On 12/13/17 22:31, blubee blubeeme wrote:
On Thu, Dec 14, 2017 at 11:17 AM, Pedro Giffuni > wrote:


Hello;
On 13/12/2017 21:11, Chris H wrote:
On Wed, 13 Dec 2017 19:56:24 -0500 "Pedro Giffuni"
 said

On 12/10/17 14:55, Eugene Grosbein wrote:

11.12.2017 2:22, Pedro Giffuni пишет:

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 in 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=linux", "USE_LINUX_RPM=yes" and make

these two files

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?= ${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=yes".
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 Centos repositories?

    Just a thought, and hope it helps!

Thanks, I just have to keep digging :(.

Pedro.

The linux packaging is okay but I'd recommend learning how the 
porting process and not just wrapping up a linux binary in FreeBSD.




Well ... of course if I had the source code I would not be dealing 
RPMs for the linuxulator.


Software can be free but not include source code.  It can still be 
desirable for 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.




Which is why we have a linuxulator.

OK Pedro, just so I know I understand your intentions correctly;
You need a way to unpack all the .rpm's, and separate them by
$arch -- 32bit -vs- 64bit, so that you can create the correct 
pkg-plist(s)

for each of them. Is that correct?

I'll await your response before a solution for that.



I did that already, thanks.
The trick was defining DISTFILES_amd64, DISTFILES_i386 and SRC_DISTFILES.

Now the problem is that our RPM support doesn't expect to find files 
installed in usr/bin and share.


At some point I decided it was better to use the .tar.xz distribution 
but that uses version of glibc and libpng that don't match either of the 
centos distributions we carry. So I am back to RPMs.


Cheers,

Pedro.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Linux ports tutorial? WPS Office

[Pedro Giffuni]

On 12/14/17 18:11, Chris H wrote:

On Thu, 14 Dec 2017 17:59:34 -0500 "Pedro Giffuni"  said


On 12/14/17 17:07, Chris H wrote:
> On Thu, 14 Dec 2017 09:15:35 -0500 "Pedro Giffuni" 
 said

>> On 12/13/17 22:31, blubee blubeeme wrote:
>>> On Thu, Dec 14, 2017 at 11:17 AM, Pedro Giffuni >>> > wrote:

>>>
>>> Hello;
>>> On 13/12/2017 21:11, Chris H wrote:
>>> On Wed, 13 Dec 2017 19:56:24 -0500 "Pedro Giffuni"
>>>  said
>>>
>>> On 12/10/17 14:55, Eugene Grosbein wrote:
 11.12.2017 2:22, Pedro Giffuni пишет:
> 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 in 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=linux", "USE_LINUX_RPM=yes" and make
>>> these two files
 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?= ${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=yes".
>>> 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 Centos repositories?
>>>
>>>     Just a thought, and hope it helps!
>>>
>>> Thanks, I just have to keep digging :(.
>>>
>>> Pedro.
>>>
>>> The linux packaging is okay but I'd recommend learning how the 
>>> porting process and not just wrapping up a linux binary in FreeBSD.

>>>
>>
>> Well ... of course if I had the source code I would not be dealing 
>> RPMs for the linuxulator.

>>
>> Software can be free but not include source code.  It can still be 
>> desirable for 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.

>>>
>>
>> Which is why we have a linuxulator.
> OK Pedro, just so I know I understand your intentions correctly;
> You need a way to unpack all the .rpm's, and separate them by
> $arch -- 32bit -vs- 64bit, so that you can create the correct > 
pkg-plist(s)

> for each of them. Is that correct?
>
> I'll await your response before a solution for that.
>

I did that already, thanks.
The trick was defining DISTFILES_amd64, DISTFILES_i386 and 
SRC_DISTFILES.


Now the problem is that our RPM support doesn't expect to find files 
installed in usr/bin and share.


At some point I decided it was better to use the .tar.xz distribution 
but that uses version of glibc and libpng that don't match either of 
the centos distributions we carry. So I am back to RPMs.

Can't you just *omit* those, and use those already supplied by FreeBSD?
Maybe those in the linux_base ports, via (run|make)depends?



Yes, I did that.

The port still doesn't work:
- It appears it wants to use a old version of libpng that is not in our 
centos7.
- USE_RPM doesn't install anything, it seems like we are missing support 
for non-base RPMs.


I think I'll bail on this port, it requires some packaging-foo that I 
don't want to spend time on.


I'll leave my WIP here, for someone else to play with it:

https://people.freebsd.org/~pfg/ports/linux-wps-office.tgz

Cheers,

Pedro.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Linux ports tutorial? WPS Office

[Tijl Coosemans]

On Thu, 14 Dec 2017 18:27:10 -0500 Pedro Giffuni  wrote:
> The port still doesn't work:
> - It appears it wants to use a old version of libpng that is not in our 
> centos7.
> - USE_RPM doesn't install anything, it seems like we are missing support 
> for non-base RPMs.
> 
> I think I'll bail on this port, it requires some packaging-foo that I 
> don't want to spend time on.
> 
> I'll leave my WIP here, for someone else to play with it:
> 
> https://people.freebsd.org/~pfg/ports/linux-wps-office.tgz

USE_LINUX_RPM is only for Linux infrastructure ports.  You should remove
that and add your own do-install.  You also need NO_WRKSUBDIR=yes and
PLIST_SUB=LINUXBASE=${LINUXBASE}.

The do-install target should copy WRKSRC/opt and WRKSRC/usr/bin to
${STAGEDIR}${LINUXBASE}.  WRKSRC/etc and WRKSRC/usr/share look like
they should go to ${STAGEDIR}${PREFIX}.

Then you also need to add startup scripts for et, wpp and wps containing
something like this:

#! /bin/sh
exec /compat/linux/bin/sh /usr/bin/et "$@"

And let do-install copy them to ${STAGEDIR}${PREFIX/bin.

You also need to replace /usr/bin with ${PREFIX} in .desktop files.

I would also add -office to PORTNAME and remove PKGNAMESUFFIX.

The old libpng it is looking for is in CentOS 6, so USES=linux:c7 won't
work.  For now it's best to simply use USES=linux.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"