Re: Time for a firefox-56 port?

[Zhihao Yuan]

On Nov 25, 2017 8:15 PM, "Greg 'groggy' Lehey"  wrote:

It doesn't address the addon issue.  I expect that gradually the
addons will get updated to the new interfaces, so this is just a
temporary thing.


Oh, no, these addons are permanently dead, and your best hope is to find
alternatives, such as those made for Chrome.  The addons have been given 2
years to switch, and if that haven't happen, that's unlikely to happen
starting from today.  As you may know, some most famous ones have announced
death by their authors.  Given my information from Mozilla employees,
Mozilla has no motivation to make WebExtensions any more powerful to
support any addon that requires extra functionalities to port from XUL.  So
give it up, try Pale Moon.

--
Zhihao
___
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: Time for a firefox-56 port?

[Zhihao Yuan]

On Nov 25, 2017 6:31 PM, "Greg 'groggy' Lehey"  wrote:

I'm sure I'm not the only person who relies on old addons.  How about
a firefox-56 port until the current problems die down?


Here is a port for the Palemoon browser:

  https://www.freshports.org/www/palemoon/

--
Zhihao
___
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: The Original VI ?

[Zhihao Yuan]

On Sep 4, 2013 3:55 PM, Chad Perrin c...@apotheon.net wrote:
 Is there some specific reason the nvi in base is stalled so far behind
 nvi-devel in terms of usability (by the way)?

The nvi in CURRENT already supports
UTF-8; if you want varies encodings,
you need WITH_ICONV=1.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: CFT: texlive ports

[Zhihao Yuan]

On Wed, Feb 27, 2013 at 10:11 AM, Anton Shterenlikht
me...@bristol.ac.uk wrote:
 for D in /usr/local/share/texmf /usr/local/share/texmf-dist 
 /usr/local/share/texmf-local /usr/local/share/texmf-var; do  if [ -r $D/ls-R 
 ]; then /usr/local/bin/mktexlsr $D; fi;  done

Only the first dir presents on a clean installed system.  So...

-- 
Zhihao Yuan, ID lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Need help to port www/py-falcon

[Zhihao Yuan]

On Fri, Feb 22, 2013 at 9:51 AM, Zhihao Yuan lich...@gmail.com wrote:
 If I set

   USE_PYDISTUTILS=easy_install

 then I got

   ===   Generating temporary packing list
   running easy_install
   Creating /tmp/falcon/lib/python2.7/site-packages/site.py
   error: Not a URL, existing file, or requirement spec:
 '/home/lichray/devel/ports/www/py-falcon/work/falcon-0.1.1/dist/falcon-0.1.1-py2.7.egg'

 while my egg should be named

   falcon-0.1.1-py2.7-freebsd-8.3-STABLE-amd64.egg

Solved.

  PYEASYINSTALL_ARCHDEP=  yes

-- 
Zhihao Yuan, ID lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Need help to port www/py-falcon

[Zhihao Yuan]

Hi, hackers:

I'm porting falcon http://falconframework.org/ ,
but I found a problem with installation.

If I set

  USE_PYDISTUTILS=easy_install

then I got

  ===   Generating temporary packing list
  running easy_install
  Creating /tmp/falcon/lib/python2.7/site-packages/site.py
  error: Not a URL, existing file, or requirement spec:
'/home/lichray/devel/ports/www/py-falcon/work/falcon-0.1.1/dist/falcon-0.1.1-py2.7.egg'

while my egg should be named

  falcon-0.1.1-py2.7-freebsd-8.3-STABLE-amd64.egg

And if I set

  USE_PYDISTUTILS=easy_install

I got

  ===   Generating temporary packing list
  running install
  Checking .pth file support in /tmp/falcon/lib/python2.7/site-packages/
  error: can't create or remove files in install directory

  The following error occurred while trying to add or remove files in the
installation directory:

  [Errno 2] No such file or directory:
'/tmp/falcon/lib/python2.7/site-packages/test-easy-install-26039.pth'

I don't get it, since I have no problem to install it through `pip` or
manually run `python setup.py install` under the source tree.  I need
some help.


-- 
Zhihao Yuan, ID lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Need help to port www/py-falcon

[Zhihao Yuan]

On Fri, Feb 22, 2013 at 12:28 PM, Gary J. Hayers g...@hayers.org wrote:
 Would need to see the rest of the Makefile to help really.

The Makefile is attached.

The PYDISTUTILS_NOEGGINFO=  yes line has no use, currently.

-- 
Zhihao Yuan, ID lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/


Makefile
Description: Binary data
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Need help to port www/py-falcon

[Zhihao Yuan]

On Feb 22, 2013 2:09 PM, Gary J. Hayers g...@hayers.org wrote:
 Using /usr/local/lib/python2.7/site-packages/six-1.2.0-py2.7.egg

I'remove this dependence.  But my execution with genplist did not get me
there.

 Finished processing dependencies for falcon==0.1.1
 ===   Registering installation for py27-falcon-0.1.1
 pkg:
lstat(/usr/local/lib/python2.7/site-packages/falcon-0.1.1-py2.7.egg-info):
No such file or directory
 Installing py27-falcon-0.1.1... done

 You are running make install as root right?

Yes, with genplist.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Help my maintainer timeout PRs

[Zhihao Yuan]

Hi,

All of these are maintainer timeout.

ports/168645: [UPDATE] x11/luit to 1.1.1
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/168645

ports/172735: [UPDATE] devel/glog to 0.3.2
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/172735

This one is not under ports/, but still trivial:

bin/168415: [PATCH] stdbuf(1) does not allow cmd with no parameters
http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/168415

Thanks.

--
Zhihao Yuan, ID lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: PR missing

[Zhihao Yuan]

Hi,

I meet the same problem:

http://www.freebsd.org/cgi/query-pr.cgi?pr=173590

Category:   ports
Responsible:freebsd-ports-bugs
Synopsis:   New ports: fcitx-m17n and fcitx-unikey
Arrival-Date:   Tue Nov 13 00:20:00 UTC 2012

The PR lost.

On Wed, Nov 14, 2012 at 4:31 PM, Muhammad Moinur Rahman
5u623...@gmail.com wrote:
 Check Confidential flag.


Sorry, I don't quite understand. Isn't that always no?

-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: mplayer2 for FreeBSD

[Zhihao Yuan]

On Thu, Jul 12, 2012 at 7:03 AM, Jerry je...@seibercom.net wrote:
 I was wondering if anyone had actually attempted to compile mplayer2
 http://www.mplayer2.org/ on FreeBSD or if there was someone working
 on porting it?

I'm using it, and it seems to be a nice replace to mplayer.

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/163438


 --
 Jerry ♔

 Disclaimer: off-list followups get on-list replies or get ignored.
 Please do not ignore the Reply-To header.
 __

 We live in a world where losing your phone is more dramatic to a
 sixteen year old girl than losing her virginity.
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org



-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Xfce 4.10 on FreeBSD 9 release powerpc

[Zhihao Yuan]

On Wed, May 16, 2012 at 5:26 AM, Takashi Fujita
rina.invers...@gmail.com wrote:
 When the module which is not downloadable was copied to the folder which
 referred to google and was specified, building started.

 The screen of Xfce was displayed when it started instantly, since building
 was successful.

 About two problems have occurred.

 -There are two or more parts (it is x) where the icon of an application menu
 is not displayed.

Yes. Because your icon theme  hicolor do not have those. It's OK.


 -The reboot and shutdown by a general user cannot be performed.

Check /usr/ports/x11-wm/xfce4-session/pkg-message

BTW, this file should be .in; %%LOCALBASE%% is not replaced.


 If the correspondence method is carried out now [ familiar / direction ]
 about these two points, please let me know.


 (2012/05/15 23:01), Zhihao Yuan wrote:

 On Tue, May 15, 2012 at 8:52 AM, Takashi Fujita
 rina.invers...@gmail.com  wrote:

 Thank you for the correspondence.
 May the following methods be used although it is the order of the real
 way
 of a script?

 1.execute xfcemerge
 2.cd /usr/ports/x11/xfce4
 3.make clean
 4.make install clean


 You may want to try:
 sudo xfcemerge
  - followed by -
 sudo portmaster -a

 portmaster will handle the upgrade order according to the dependencies.


 If there is a file deleted beforehand, please let me know.


 (12/05/15 22:37), Zhihao Yuan wrote:


 On Tue, May 15, 2012 at 7:50 AM, Takashi Fujita
 rina.invers...@gmail.com    wrote:


 After deleting a file, when make install clean was performed again, the
 following errors came out and compile was interrupted.

 ==Patching for xfce4-session-4.10.0
 ==Applying FreeBSD patches for xfce4-session-4.10.0
 1 out of 1 hunks ignored--saving rejects to
 xfce4-session/xfsm-shutdown-helper.c.rej
 =Patch patch-xfce4-session_xfsm-shutdown-helper.c failed to apply
 cleanly.


 (2012/05/15 21:26), Zhihao Yuan wrote:



 On Tue, May 15, 2012 at 7:21 AM, Takashi Fujita
 rina.invers...@gmail.com      wrote:



 M9686J/A Mac mini G4 FreeBSD 9-Release is installed in 1.25 GHz.

 The following contribution tends to be seen and it is going to
 install
 Xfce4.10 in this environment.

 Hi folks,

 I've updated the xfce-4.10 tarball [1] (it contains only the latest
 versions of Xfce4 core).
 Changes :
 - Delete thunarvfs in bsd.xfce.mk, because this library now, is
 obsolete, even if it always used by archiver/squeeze (no update
 since
 4 years).
 - Drop support of GTK3 in x11-themes/gtk-xfce-engine

 I've also add shell script 'xfcemerge' [2] (based on marcusmerge and
 kdemerge) to easily update ports tree. It works with tarball and
 with
 my repository.

 In my repository we can found the latest versions of :
 - x11/xfce4-screenshooter-plugin,
 http://www.freebsd.org/cgi/query-pr.cgi?pr=167537
 - www/midori, http://www.freebsd.org/cgi/query-pr.cgi?pr=167536
 - sysutils/xfce4-battery-plugin (1.0.2)
 - sysutils/xfce4-systemload-plugin (1.1.0)
 - x11-clocks/xfce4-timer-out-plugin (1.0.1)
 - graphics/ristretto (0.6.0)

 Enjoy

 [1] http://xfce-ports.googlecode.com/files/xfce-4.10.tar.xz
 [2] http://xfce-ports.googlecode.com/files/xfcemerge


 shell script'xfcemerge' was performed and port tree was updated.

 When
 [cd /usr/ports/x11-wm/xfce4]
 [make config-recursive]
 [make install clean]
 and a command are executed after that, the following error comes out
 and
 compile goes wrong.

 ===        Installing for xfce-4.10
 ===         xfce-4.10 depends on executable: xfwm4 - not found
 ===          Verifying install for xfwm4 in
 /usr/ports/x11-wm/xfce4-wm
 ===        Patching for xfce4-wm-4.10.0
 ===        Applying FreeBSD patches for xfce4-wm-4.10.0
 File to patch:
 No file found--skip this patch? [n]y
 2 out of 2 hunks ignored--saving rehects to
 doc/manual/images/Makefile.in.rej
 Can't create doc/manual/images/Makefile.in.rej, output is in
 /tmp/patchrvHLsNE: No such file or directory
 =      Patch patch-doc_manual_images_Makefile.in failed to apply
 cleanly.
 *** Error code 1

 Stop in /usr/ports/x11-wm/xfce4-wm.
 *** Error code 1

 Stop in /usr/ports/x11-wm/xfce4-wm.
 *** Error code 1

 Stop in /usr/ports/x11-wm/xfce4.
 *** Error code 1

 Stop in /usr/ports/x11-wm/xfce4.

 --
 Takashi Fujita
 rina.invers...@gmail.com
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to
 freebsd-ports-unsubscr...@freebsd.org




 As I said, the xfcemerge script does not remove old files. So please
 remove any file under xfce4-wm/files except extrapatch-src__events.c.



 --
 Takashi Fujita
 rina.invers...@gmail.com
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to
 freebsd-ports-unsubscr...@freebsd.org



 I see. I'll fix this. Try the new xfcemerge script attached

Re: Xfce 4.10 on FreeBSD 9 release powerpc

[Zhihao Yuan]

On Wed, May 16, 2012 at 6:13 AM, Takashi Fujita
rina.invers...@gmail.com wrote:
 (2012/05/16 19:44), Zhihao Yuan wrote:

 On Wed, May 16, 2012 at 5:26 AM, Takashi Fujita
 rina.invers...@gmail.com  wrote:

 When the module which is not downloadable was copied to the folder which
 referred to google and was specified, building started.

 The screen of Xfce was displayed when it started instantly, since
 building
 was successful.

 About two problems have occurred.

 -There are two or more parts (it is x) where the icon of an application
 menu
 is not displayed.

 Yes. Because your icon theme  hicolor do not have those. It's OK.

 What should be done for improving this state?


 -The reboot and shutdown by a general user cannot be performed.


 Check /usr/ports/x11-wm/xfce4-session/pkg-message

 Do I hear that this application is installed?

Unfortunately, Olivier used an uncommon method which makes you can
only see this message after pkg_add, not after make install.



 BTW, this file should be .in; %%LOCALBASE%% is not replaced.

 Would you teach a little in more detail?

Olivier used ${SED} here. A better approach is to set
SUB_FILES=  pkg-message
and to add
@${CAT} ${PKGMESSAGE}
in post-install.

To enable shutdown/restart, just replace 'PUTYOURGROUPHERE' with your
own user group, and create a .pkla file under
/usr/local/etc/polkit-1/localauthority/50-local.d (use mkdir -p to
create this).




 --
 Takashi Fujita
 rina.invers...@gmail.com
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org



-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Xfce 4.10 on FreeBSD 9 release powerpc

[Zhihao Yuan]

On Tue, May 15, 2012 at 7:21 AM, Takashi Fujita
rina.invers...@gmail.com wrote:
 M9686J/A Mac mini G4 FreeBSD 9-Release is installed in 1.25 GHz.

 The following contribution tends to be seen and it is going to install
 Xfce4.10 in this environment.

 Hi folks,

 I've updated the xfce-4.10 tarball [1] (it contains only the latest
 versions of Xfce4 core).
 Changes :
 - Delete thunarvfs in bsd.xfce.mk, because this library now, is
 obsolete, even if it always used by archiver/squeeze (no update since
 4 years).
 - Drop support of GTK3 in x11-themes/gtk-xfce-engine

 I've also add shell script 'xfcemerge' [2] (based on marcusmerge and
 kdemerge) to easily update ports tree. It works with tarball and with
 my repository.

 In my repository we can found the latest versions of :
 - x11/xfce4-screenshooter-plugin,
 http://www.freebsd.org/cgi/query-pr.cgi?pr=167537
 - www/midori, http://www.freebsd.org/cgi/query-pr.cgi?pr=167536
 - sysutils/xfce4-battery-plugin (1.0.2)
 - sysutils/xfce4-systemload-plugin (1.1.0)
 - x11-clocks/xfce4-timer-out-plugin (1.0.1)
 - graphics/ristretto (0.6.0)

 Enjoy

 [1] http://xfce-ports.googlecode.com/files/xfce-4.10.tar.xz
 [2] http://xfce-ports.googlecode.com/files/xfcemerge


 shell script'xfcemerge' was performed and port tree was updated.

 When
 [cd /usr/ports/x11-wm/xfce4]
 [make config-recursive]
 [make install clean]
 and a command are executed after that, the following error comes out and
 compile goes wrong.

 ===  Installing for xfce-4.10
 ===   xfce-4.10 depends on executable: xfwm4 - not found
 ===    Verifying install for xfwm4 in /usr/ports/x11-wm/xfce4-wm
 ===  Patching for xfce4-wm-4.10.0
 ===  Applying FreeBSD patches for xfce4-wm-4.10.0
 File to patch:
 No file found--skip this patch? [n]y
 2 out of 2 hunks ignored--saving rehects to
 doc/manual/images/Makefile.in.rej
 Can't create doc/manual/images/Makefile.in.rej, output is in
 /tmp/patchrvHLsNE: No such file or directory
 = Patch patch-doc_manual_images_Makefile.in failed to apply cleanly.
 *** Error code 1

 Stop in /usr/ports/x11-wm/xfce4-wm.
 *** Error code 1

 Stop in /usr/ports/x11-wm/xfce4-wm.
 *** Error code 1

 Stop in /usr/ports/x11-wm/xfce4.
 *** Error code 1

 Stop in /usr/ports/x11-wm/xfce4.

 --
 Takashi Fujita
 rina.invers...@gmail.com
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

As I said, the xfcemerge script does not remove old files. So please
remove any file under xfce4-wm/files except extrapatch-src__events.c.

-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Xfce 4.10 on FreeBSD 9 release powerpc

[Zhihao Yuan]

On Tue, May 15, 2012 at 7:50 AM, Takashi Fujita
rina.invers...@gmail.com wrote:
 After deleting a file, when make install clean was performed again, the
 following errors came out and compile was interrupted.

 ==Patching for xfce4-session-4.10.0
 ==Applying FreeBSD patches for xfce4-session-4.10.0
 1 out of 1 hunks ignored--saving rejects to
 xfce4-session/xfsm-shutdown-helper.c.rej
 =Patch patch-xfce4-session_xfsm-shutdown-helper.c failed to apply cleanly.


 (2012/05/15 21:26), Zhihao Yuan wrote:

 On Tue, May 15, 2012 at 7:21 AM, Takashi Fujita
 rina.invers...@gmail.com  wrote:

 M9686J/A Mac mini G4 FreeBSD 9-Release is installed in 1.25 GHz.

 The following contribution tends to be seen and it is going to install
 Xfce4.10 in this environment.

 Hi folks,

 I've updated the xfce-4.10 tarball [1] (it contains only the latest
 versions of Xfce4 core).
 Changes :
 - Delete thunarvfs in bsd.xfce.mk, because this library now, is
 obsolete, even if it always used by archiver/squeeze (no update since
 4 years).
 - Drop support of GTK3 in x11-themes/gtk-xfce-engine

 I've also add shell script 'xfcemerge' [2] (based on marcusmerge and
 kdemerge) to easily update ports tree. It works with tarball and with
 my repository.

 In my repository we can found the latest versions of :
 - x11/xfce4-screenshooter-plugin,
 http://www.freebsd.org/cgi/query-pr.cgi?pr=167537
 - www/midori, http://www.freebsd.org/cgi/query-pr.cgi?pr=167536
 - sysutils/xfce4-battery-plugin (1.0.2)
 - sysutils/xfce4-systemload-plugin (1.1.0)
 - x11-clocks/xfce4-timer-out-plugin (1.0.1)
 - graphics/ristretto (0.6.0)

 Enjoy

 [1] http://xfce-ports.googlecode.com/files/xfce-4.10.tar.xz
 [2] http://xfce-ports.googlecode.com/files/xfcemerge


 shell script'xfcemerge' was performed and port tree was updated.

 When
 [cd /usr/ports/x11-wm/xfce4]
 [make config-recursive]
 [make install clean]
 and a command are executed after that, the following error comes out and
 compile goes wrong.

 ===    Installing for xfce-4.10
 ===     xfce-4.10 depends on executable: xfwm4 - not found
 ===      Verifying install for xfwm4 in /usr/ports/x11-wm/xfce4-wm
 ===    Patching for xfce4-wm-4.10.0
 ===    Applying FreeBSD patches for xfce4-wm-4.10.0
 File to patch:
 No file found--skip this patch? [n]y
 2 out of 2 hunks ignored--saving rehects to
 doc/manual/images/Makefile.in.rej
 Can't create doc/manual/images/Makefile.in.rej, output is in
 /tmp/patchrvHLsNE: No such file or directory
 =  Patch patch-doc_manual_images_Makefile.in failed to apply cleanly.
 *** Error code 1

 Stop in /usr/ports/x11-wm/xfce4-wm.
 *** Error code 1

 Stop in /usr/ports/x11-wm/xfce4-wm.
 *** Error code 1

 Stop in /usr/ports/x11-wm/xfce4.
 *** Error code 1

 Stop in /usr/ports/x11-wm/xfce4.

 --
 Takashi Fujita
 rina.invers...@gmail.com
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


 As I said, the xfcemerge script does not remove old files. So please
 remove any file under xfce4-wm/files except extrapatch-src__events.c.



 --
 Takashi Fujita
 rina.invers...@gmail.com
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

I see. I'll fix this. Try the new xfcemerge script attached.

-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/


xfcemerge
Description: Binary data
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Xfce 4.10 on FreeBSD 9 release powerpc

[Zhihao Yuan]

On Tue, May 15, 2012 at 8:52 AM, Takashi Fujita
rina.invers...@gmail.com wrote:
 Thank you for the correspondence.
 May the following methods be used although it is the order of the real way
 of a script?

 1.execute xfcemerge
 2.cd /usr/ports/x11/xfce4
 3.make clean
 4.make install clean

You may want to try:
sudo xfcemerge
 - followed by -
sudo portmaster -a

portmaster will handle the upgrade order according to the dependencies.


 If there is a file deleted beforehand, please let me know.


 (12/05/15 22:37), Zhihao Yuan wrote:

 On Tue, May 15, 2012 at 7:50 AM, Takashi Fujita
 rina.invers...@gmail.com  wrote:

 After deleting a file, when make install clean was performed again, the
 following errors came out and compile was interrupted.

 ==Patching for xfce4-session-4.10.0
 ==Applying FreeBSD patches for xfce4-session-4.10.0
 1 out of 1 hunks ignored--saving rejects to
 xfce4-session/xfsm-shutdown-helper.c.rej
 =Patch patch-xfce4-session_xfsm-shutdown-helper.c failed to apply
 cleanly.


 (2012/05/15 21:26), Zhihao Yuan wrote:


 On Tue, May 15, 2012 at 7:21 AM, Takashi Fujita
 rina.invers...@gmail.com    wrote:


 M9686J/A Mac mini G4 FreeBSD 9-Release is installed in 1.25 GHz.

 The following contribution tends to be seen and it is going to install
 Xfce4.10 in this environment.

 Hi folks,

 I've updated the xfce-4.10 tarball [1] (it contains only the latest
 versions of Xfce4 core).
 Changes :
 - Delete thunarvfs in bsd.xfce.mk, because this library now, is
 obsolete, even if it always used by archiver/squeeze (no update since
 4 years).
 - Drop support of GTK3 in x11-themes/gtk-xfce-engine

 I've also add shell script 'xfcemerge' [2] (based on marcusmerge and
 kdemerge) to easily update ports tree. It works with tarball and with
 my repository.

 In my repository we can found the latest versions of :
 - x11/xfce4-screenshooter-plugin,
 http://www.freebsd.org/cgi/query-pr.cgi?pr=167537
 - www/midori, http://www.freebsd.org/cgi/query-pr.cgi?pr=167536
 - sysutils/xfce4-battery-plugin (1.0.2)
 - sysutils/xfce4-systemload-plugin (1.1.0)
 - x11-clocks/xfce4-timer-out-plugin (1.0.1)
 - graphics/ristretto (0.6.0)

 Enjoy

 [1] http://xfce-ports.googlecode.com/files/xfce-4.10.tar.xz
 [2] http://xfce-ports.googlecode.com/files/xfcemerge


 shell script'xfcemerge' was performed and port tree was updated.

 When
 [cd /usr/ports/x11-wm/xfce4]
 [make config-recursive]
 [make install clean]
 and a command are executed after that, the following error comes out
 and
 compile goes wrong.

 ===      Installing for xfce-4.10
 ===       xfce-4.10 depends on executable: xfwm4 - not found
 ===        Verifying install for xfwm4 in /usr/ports/x11-wm/xfce4-wm
 ===      Patching for xfce4-wm-4.10.0
 ===      Applying FreeBSD patches for xfce4-wm-4.10.0
 File to patch:
 No file found--skip this patch? [n]y
 2 out of 2 hunks ignored--saving rehects to
 doc/manual/images/Makefile.in.rej
 Can't create doc/manual/images/Makefile.in.rej, output is in
 /tmp/patchrvHLsNE: No such file or directory
 =    Patch patch-doc_manual_images_Makefile.in failed to apply
 cleanly.
 *** Error code 1

 Stop in /usr/ports/x11-wm/xfce4-wm.
 *** Error code 1

 Stop in /usr/ports/x11-wm/xfce4-wm.
 *** Error code 1

 Stop in /usr/ports/x11-wm/xfce4.
 *** Error code 1

 Stop in /usr/ports/x11-wm/xfce4.

 --
 Takashi Fujita
 rina.invers...@gmail.com
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to
 freebsd-ports-unsubscr...@freebsd.org



 As I said, the xfcemerge script does not remove old files. So please
 remove any file under xfce4-wm/files except extrapatch-src__events.c.



 --
 Takashi Fujita
 rina.invers...@gmail.com
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


 I see. I'll fix this. Try the new xfcemerge script attached.


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



-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: [CFT] Xfce 4.10

[Zhihao Yuan]

Tested using xfcemerge; Thunar untested.

Great one-man-show!

2 tiny problems:
1. In bsd.xfce.mk, -L is a LDFLAGS, not CPPFLAGS. I saw too many clang
'unused option' warnings during the compilation;
2. The xfcemerge does not delete files. the files/ dir under
xfce4-systemload is removed, right?

On Tue, May 8, 2012 at 2:27 PM, Torfinn Ingolfsen tin...@gmail.com wrote:
 On Sat, May 5, 2012 at 7:30 PM, Olivier Duchateau
 duchateau.oliv...@gmail.com wrote:
 Hi folks,

 I've updated the xfce-4.10 tarball [1] (it contains only the latest
 versions of Xfce4 core).
 Changes :
 - Delete thunarvfs in bsd.xfce.mk, because this library now, is
 obsolete, even if it always used by archiver/squeeze (no update since
 4 years).

 How are we supposed to get squeeze to install now?
 It fails:
 ===   xfce-4.10 depends on executable: squeeze - not found
 ===    Verifying install for squeeze in /usr/ports/archivers/squeeze
 ===  squeeze-0.2.3_2 cannot install: Unknown component thunarvfs.
 *** Error code 1

 Stop in /usr/ports/archivers/squeeze.
 *** Error code 1

 Stop in /usr/ports/x11-wm/xfce4.
 *** Error code 1

 Stop in /usr/ports/x11-wm/xfce4.




 --
 Regards,
 Torfinn Ingolfsen
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org



-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: New X.Org

[Zhihao Yuan]

On Mon, Apr 23, 2012 at 6:49 AM, Andrea Venturoli m...@netfence.it wrote:
 Hello.

 I see in UPDATING

 The default mesa has been updated to 7.6.1 and the default xorg-server
  to 1.7.7.
  A switch is available for people that want to use mesa 7.11.x and
  xorg-server 1.10.6. This requires an nvidia card or Intel+KMS support.


 I have a Radeon card, so, does this mean I will get xorg-server? Any way to
 get 1.10? Any advantage into this?

 Also, I have WITHOUT_NOUVEAU in /etc/make.conf. Should I remove it?

This flag only applies to Mesa, and it's no longer used. The new
WITH_NEW_XORG applies to both xorg-server and Mesa.


 Thought I just asked, before risking to blow everything up :)

  bye  Thanks
        av.
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org



-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: New X.Org

[Zhihao Yuan]

On Mon, Apr 23, 2012 at 9:28 AM, matt sendtom...@gmail.com wrote:
 On 04/23/12 05:59, Warren Block wrote:
 On Mon, 23 Apr 2012, Andrea Venturoli wrote:

 I have a Radeon card, so, does this mean I will get xorg-server? Any
 way to get 1.10? Any advantage into this?

 A Radeon 4650 is working fine here with xorg-server 1.10.6 and mesa
 7.11.  So far there are no Firefox title bar artifacts like there were
 occasionally with the earlier version.

 Also, I have WITHOUT_NOUVEAU in /etc/make.conf. Should I remove it?

 Yes, replace it with WITH_NEW_XORG=yes.  Then rebuild graphics/libdrm,
 xorg-server, xf86-input-*, xf86-video-*, and... a few other things I
 should have taken notes on.
 ___
 freebsd-...@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-x11
 To unsubscribe, send any mail to freebsd-x11-unsubscr...@freebsd.org
 Interesting. Another Radeon 4650 (rv730) is not working here, giving Bus
 Errors at the same address whenever certain applications are launched.
 Failing examples: Firefox, gedit, qt4-designer
 Successful: xfce4-terminal, ioquake3, compiz

 I just completed recompiling all ports dependent on libGL with no luck.
 I had WITHOUT_NOUVEAU in make.conf at the same time as
 WITH_NEW_XORG, is that the problem?

WITHOUT_NOUVEAU has no effect; only WITH_NEW_XORG has.
Any crash log? Xorg.0.log?

 Does this sound like an Xorg problem or a ports/ld problem?

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



-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Re: recent portrevision bump for libvpx

[Zhihao Yuan]

On Fri, Feb 17, 2012 at 7:59 AM, Mikhail T. mi+t...@aldan.algebra.com wrote:
 On -10.01.-28163 14:59, Jakub Lach wrote:

 Speaking of recent libvpx update, some ports explicitly look
 for libvpx.so.0, and fail to update trying to install again libvpx
 which is already installed.

 e.g. multimedia/gstreamer-plugins-vp8

 Yet again I'd like to point out, that -- contrary to the wide-spread
 practice -- ports should not, by default, list a particular shlib major
 number in LIB_DEPENDS. Only in cases, when a wrong version of some libfoo is
 known to cause problems, should the correct version be explicitly given in
 LIB_DEPENDS.

I regard this as a wrong practice. Here is why:

1. The way you specify the version in LIB_DEPENDS has NO relation with
how the port link to the lib. The port can link to the major version
(pkg-config), or the .so, etc.

2. One responsibility of the ports system is to protect the user from
suffering from running a software which links to a ABI incompatible,
hence, wrong shared library. A software runs incorrectly is a
disaster, and the shared library version is to prevent this, and the
ports system is to protect the versioned shared libraries. Thus -- A
port fails to find its depends better than it does not link, a
software does not link is better than it does not run correctly. And
your practice is trying to remove such protection.

3. Known to cause problem? Can I infer you can predict the future
from that?

So, to link to a version explicitly should be the default. Only a
library behaviors good in its development history can be considered
to use it's libname only in LIB_DEPENDS.


   -mi


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



-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: recent portrevision bump for libvpx

[Zhihao Yuan]

On Fri, Feb 17, 2012 at 2:57 PM, Mikhail T. mi+t...@aldan.algebra.com wrote:
 On 17.02.2012 14:24, Zhihao Yuan wrote:

 I regard this as a wrong practice. Here is why:

 1. The way you specify the version in LIB_DEPENDS has NO relation with
 how the port link to the lib. The port can link to the major version
 (pkg-config), or the .so, etc.

 I'm sorry, I can not parse the above part. Perhaps, a live example is in
 order.

LIB_DEPENDS= png.6: or =png: does not affect how the lib got linked.
It always links to the latest libpng the time you compile the port.


 2. One responsibility of the ports system is to protect the user from
 suffering from running a software which links to a ABI incompatible,
 hence, wrong shared library.

 This is a made-up non-reason, sorry. The only way to get into an ABI
 incompatibility is to have -- at the time of the port building --
 header-files declarations from one version of a library and
 implementation(s) from another. Avoiding such situations is out of the scope
 of the ports-system and this discussion.

 Again, try to come up with a real-life example of how my proposal would
 break ABI for an actual user... You can not.

This only happens when a minor version of a library is not compatible
with another one. OK, that's out of the scope.


 3. Known to cause problem? Can I infer you can predict the future
 from that?

 Yes, you can. Well-knowing the past 15 or so years of the ports-system, I
 can predict some aspects of the future. For example:

 committers will continue to forget to update some of the umpteen instances
 of LIB_DEPENDS=foo.X in various ports, when bumping up major version of foo.
 committers will continue to mindlessly bump-up these umpteen instances --
 without actually verifying, that the new version of foo is still acceptable
 to all of those dependants.

My opinion is that, fails to build is not a big trouble, at least we
notified the through portsnap/pkg_version; The user surprisingly finds
that his software fails to run is a bigger trouble.

 port-building will remain unduly difficult because of the wide-spread
 mindless (mis)use of the major shlib-number in LIB_DEPENDS. Consider the
 following scenario (substitute any of png, jpeg, xml, etc. for foo):

The updates to major libs always bind to a larger updates in the ports
tree. You have to upgrade all of the ports depend on them no matter
how you use LIB_DEPENDS.


 You build a shiny new machine -- with the desktop of your choice (KDE,
 Gnome, Xfce - whatever) from ports. Hours of build-time interrupted by
 occasional `config' screens...
 A week later you update your ports tree -- which sees version-bump of
 libfoo.
 You try to add a foo-using program bar to your computer -- and fail, because
 the bar-port now insists on the very latest version of libfoo. Not because
 the maintainer of bar determined, that the earlier versions are bad --
 simply because the maintainer of foo went through all dependents and updated
 the LIB_DEPENDS lines in all of them, as is the current sad practice.
 You now have to either portupgrade libfoo -- which means, your desktop will
 be using libfoo.N and the newly-built bar will be using libfoo.N+1
 (inefficient and sometimes a source of problems in its own), or go through
 rebuilding all of the foo-using ports again...

I regards what you said above as the regular routine, and I can't see
how your practice can improve such a routine.


 So, to link to a version explicitly should be the default. Only a
 library behaviors good in its development history can be considered
 to use it's libname only in LIB_DEPENDS.

 I'm not sure, what you mean by link to a version. Once again, I beg you to
 offer a live example. Yours,

I mean LIB_DEPENDS= png.6


 -mi



-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: recent portrevision bump for libvpx

[Zhihao Yuan]

On Feb 17, 2012 5:17 PM, Mikhail T. mi+t...@aldan.algebra.com wrote:

 On 17.02.2012 17:05, Zhihao Yuan wrote:

 On Fri, Feb 17, 2012 at 2:57 PM, Mikhail T. mi+t...@aldan.algebra.com
wrote:

 On 17.02.2012 14:24, Zhihao Yuan wrote:

 I regard this as a wrong practice. Here is why:

 1. The way you specify the version in LIB_DEPENDS has NO relation with
 how the port link to the lib. The port can link to the major version
 (pkg-config), or the .so, etc.

 I'm sorry, I can not parse the above part. Perhaps, a live example is in
 order.

 LIB_DEPENDS= png.6: or =png: does not affect how the lib got linked.
 It always links to the latest libpng the time you compile the port.

 Yes, this is correct. But irrelevant, really -- this will remain true,
whether or not LIB_DEPENDS lines contain explicit library numbers.


 2. One responsibility of the ports system is to protect the user from
 suffering from running a software which links to a ABI incompatible,
 hence, wrong shared library.

 This is a made-up non-reason, sorry. The only way to get into an ABI
 incompatibility is to have -- at the time of the port building --
 header-files declarations from one version of a library and
 implementation(s) from another. Avoiding such situations is out of the
scope
 of the ports-system and this discussion.

 Again, try to come up with a real-life example of how my proposal would
 break ABI for an actual user... You can not.

 This only happens when a minor version of a library is not compatible
 with another one. OK, that's out of the scope.


 We have not used minor library versions since switch-over to ELF... I do
not understand, what you are talking about.




 3. Known to cause problem? Can I infer you can predict the future
 from that?

 Yes, you can. Well-knowing the past 15 or so years of the ports-system,
I
 can predict some aspects of the future. For example:

 committers will continue to forget to update some of the umpteen
instances
 of LIB_DEPENDS=foo.X in various ports, when bumping up major version of
foo.
 committers will continue to mindlessly bump-up these umpteen instances
--
 without actually verifying, that the new version of foo is still
acceptable
 to all of those dependants.

 My opinion is that, fails to build is not a big trouble, at least we
 notified the through portsnap/pkg_version; The user surprisingly finds
 that his software fails to run is a bigger trouble.

 The existing practice does not protect against this bigger trouble
either -- whenever port installing libfoo.so is updated, all of the ports
LIB_DEPENDing on foo.X are matter-of-factly updated to LIB_DEPEND on
foo.(X+1). At best, these  updates are verified to continue to build -- but
they are never verified to continue to work -- although they usually do
work, of course.

 `cvs log' shows thousands of commit messages matching the pattern
chas.*bump (libvpx included, of course) -- I'd be surprised to learn, the
usability test was conducted in 1% of these cases...



 port-building will remain unduly difficult because of the wide-spread
 mindless (mis)use of the major shlib-number in LIB_DEPENDS. Consider the
 following scenario (substitute any of png, jpeg, xml, etc. for
foo):

 The updates to major libs always bind to a larger updates in the ports
 tree. You have to upgrade all of the ports depend on them no matter
 how you use LIB_DEPENDS.

 No, I should not have to. I might prefer to, but I should not be forced
to do it. And what's a major lib anyway? Does x264 qualify? If I want to
add vlc, for example, do you want to force me to rebuild mplayer as well --
because x264 went from 137 to 171 since I last built it?



 You build a shiny new machine -- with the desktop of your choice (KDE,
 Gnome, Xfce - whatever) from ports. Hours of build-time interrupted by
 occasional `config' screens...
 A week later you update your ports tree -- which sees version-bump of
 libfoo.
 You try to add a foo-using program bar to your computer -- and fail,
because
 the bar-port now insists on the very latest version of libfoo. Not
because
 the maintainer of bar determined, that the earlier versions are bad --
 simply because the maintainer of foo went through all dependents and
updated
 the LIB_DEPENDS lines in all of them, as is the current sad practice.
 You now have to either portupgrade libfoo -- which means, your desktop
will
 be using libfoo.N and the newly-built bar will be using libfoo.N+1
 (inefficient and sometimes a source of problems in its own), or go
through
 rebuilding all of the foo-using ports again...

 I regards what you said above as the regular routine, and I can't see
 how your practice can improve such a routine.


 If the port bar is willing to compile against any version of libfoo (and
the vast majority of ports are), then the problem I described will not
strike anyone -- bar will built against whatever libfoo is already
installed on the building computer, and that's it. The user still has an
option to upgrade everything

Re: Library numbers in LIB_DEPENDS considered harmful (Re: recent portrevision bump for libvpx)

[Zhihao Yuan]

On Feb 17, 2012 5:41 PM, Mikhail T. mi+t...@aldan.algebra.com wrote:

 On 17.02.2012 17:05, Zhihao Yuan wrote:

 LIB_DEPENDS= png.6: or =png: does not affect how the lib got linked.

 Allow me to rephrase my argument from a different perspective...

 The language used in our ports' Makefiles is, largely, declarative --
various things are declared and then bsd.port.mk (and friends) interpret
them to do the right thing.

 Each declaration is meant to say something, so let's examine, what a
LIB_DEPENDS entry declares:

 LIB_DEPENDS=foo.V:${PORTSDIR}/cat/libfoo

 The above line says, that this port needs a shared library libfoo.so.V to
be installed. It also says, how to install it, if it is not already present
at build-time.

 If, in fact, the current port does not care, which version of libfoo is
uses -- and most software does not -- then declaring an explicit V is
wrong: it gratuitously tightens the build-time requirements. Unless a
particular version is, indeed, required, the above line should read simply:

 LIB_DEPENDS=foo:${PORTSDIR}/cat/libfoo

 Let's say, you sent someone to buy a bottle of dry red wine in a store.
Wouldn't you be (unpleasantly) surprised, if he returned empty-handed,
because the store did not have any Californian Pinot Noir of the 2003
vintage? Huh? You did not ask for Pinot Noir. You did not specify the
origin nor the year either -- why did not he get something else that
matched your much wider and easier-to-satisfy requirement: dry red wine?

So what, I come to your bar and say 10 year red wine in1998, you give me
a 1988 one. And I went your place again in 2008, and say same wine, and
you give me a 1998 one?


 A similar thing happens here: if the, say, vlc software needs libx264 to
be available at build time, the FreeBSD port of vlc should not add a
requirement of a particular version to that.

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

Re: FreeBSD Port: x11-wm/compiz

[Zhihao Yuan]

Try to put a %%GNOME%% in front of each file that appears conditionally in
pkg-plist, and PLIST_SUB it. Good luck.

--
Zhihao Yuan
On Feb 16, 2012 9:39 AM, Ashley Diamond a...@diamondbsd.com wrote:

 I am using Compiz as a standalone window manager and am trying to build
 without gnome support to reduce dependencies. If I compile with RSVG,
 GTK, DBUS and Gnome it builds successfully. If I try to compile with
 just RSVG, GTK and DBUS it fails with:

 ===   Running ldconfig
 /sbin/ldconfig -m /usr/local/lib
 ===   Registering installation for compiz-0.8.4_7

 === Creating a package for new version compiz-0.8.4_7
 tar: share/applications/compiz.desktop: Cannot stat: No such file or
 directory
 tar: Error exit delayed from previous errors.
 pkg_create: make_dist: tar command failed with code 256

 === Package creation of compiz-0.8.4_7 failed
 === Aborting update

 Terminated

 === You can restart from the point of failure with this command line:
   portmaster flags x11-wm/compiz

 I assume either you *have* to install with Gnome (if so why is it an
 option) or reference to the compiz.desktop needs to be removed when not
 using Gnome?

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

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

Re: cannot build x11-wm/xfce4-wm after upgrade x11/xcb-util

[Zhihao Yuan]

On Tue, Jan 17, 2012 at 10:39 PM, Heino Tiedemann
rotkaps_spam_t...@gmx.de wrote:
 Michael Johnson a...@ahze.net wrote:

 Out of curiosity, what does 'grep xcb-aux /usr/local/libdata/pkgconfig/*'
 show?

 Nothing. No Output.

 Heino

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

I solved this problem by rebuilding libxfce4menu (to update the
libtool profile).

-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: CFT: mplayer and mencoder updates

[Zhihao Yuan]

On Fri, Dec 30, 2011 at 3:27 AM, Jan Beich jbe...@tormail.net wrote:
 Zhihao Yuan lich...@gmail.com writes:

 Zhihao Yuan lich...@gmail.com writes:

 On Thu, Dec 29, 2011 at 6:07 PM, Thomas Zander
 thomas.e.zan...@googlemail.com wrote:
 Hi,

 thank you all for your comments on the first iteration of the ports.
 A heavily revised version can be found on
 http://www.rrr.de/~riggs/mplayer/m20111230.tar.bz2

 Changes:
 [...]
 - use newer gcc and binutils thus enabling significant speed-ups (and
 also, since most mplayer and ffmpeg development is done on newer gcc
 and binutils than we have in the base system, it's slowly getting
 tedious to ensure compatibility with older toolchain)

 So, with the new toolchain --disable-ssse3 is dropped but why
 BROKEN_RELOCATIONS is still there?


 GJ. Tested with clang, no problem either.

 Even though the port now explicitly uses gcc, ignoring CC from make.conf
 or Makefile.local ? And on clang with -integrated-as being default gnu as
 is not used, e.g. try to remove /usr/bin/as, it'd still build fine.

 It's not ignoring CC. It sets USE_GCC=, which can be overwrite by make 
 CC=clang.

 Have you actually tried ? It's a known blind spot for clang -exp runs.

  $ echo CC=clang Makefile.local
  $ make -V CC
  gcc46

To specify a var in command has different effect. You can  try it,
make CC=clang in mplayer dir.

-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: CFT: mplayer and mencoder updates

[Zhihao Yuan]

On Thu, Dec 29, 2011 at 8:01 PM, Jan Beich jbe...@tormail.net wrote:
 Zhihao Yuan lich...@gmail.com writes:

 On Thu, Dec 29, 2011 at 6:07 PM, Thomas Zander
 thomas.e.zan...@googlemail.com wrote:
 Hi,

 thank you all for your comments on the first iteration of the ports.
 A heavily revised version can be found on
 http://www.rrr.de/~riggs/mplayer/m20111230.tar.bz2

 Changes:
 [...]
 - use newer gcc and binutils thus enabling significant speed-ups (and
 also, since most mplayer and ffmpeg development is done on newer gcc
 and binutils than we have in the base system, it's slowly getting
 tedious to ensure compatibility with older toolchain)

 So, with the new toolchain --disable-ssse3 is dropped but why
 BROKEN_RELOCATIONS is still there?


 GJ. Tested with clang, no problem either.

 Even though the port now explicitly uses gcc, ignoring CC from make.conf
 or Makefile.local ? And on clang with -integrated-as being default gnu as
 is not used, e.g. try to remove /usr/bin/as, it'd still build fine.

It's not ignoring CC. It sets USE_GCC=, which can be overwrite by make CC=clang.

-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: CFT: mplayer and mencoder updates

[Zhihao Yuan]

On Tue, Dec 20, 2011 at 3:02 PM, Thomas Zander
thomas.e.zan...@googlemail.com wrote:
 On Tue, Dec 20, 2011 at 00:43, Zhihao Yuan lich...@gmail.com wrote:
 stable/8:

 gcc:

 ffmpeg/libavformat/libavformat.a(udp.o): In function `udp_open':
 udp.c:(.text+0xf8e): undefined reference to `pthread_create'
 ffmpeg/libavcodec/libavcodec.a(pthread.o): In function `ff_thread_init':
 pthread.c:(.text+0x178c): undefined reference to `pthread_create'
 pthread.c:(.text+0x1894): undefined reference to `pthread_create'
 collect2: ld returned 1 exit status

 How did you trigger this build problem? What OPTIONS did you use?

OCFLAGS, X11, X11XV, VDPAU, MAD, LIBCDIO.

The following is the options recorded by config.mak:

CONFIGURATION = --cc=clang --host-cc=clang --disable-bitmap-font --disab
le-liba52 --disable-ssse3 --disable-directfb --disable-faac --disable-faad --dis
able-libdca --disable-twolame --disable-x264 --disable-xvid --disable-libdirac-l
avc --disable-mencoder --disable-mpg123 --disable-alsa --disable-musepack --disa
ble-inet6 --disable-gif --disable-libopenjpeg --disable-libdv --disable-theora -
-disable-libvpx-lavc --disable-libschroedinger-lavc --disable-speex --disable-li
ve --disable-jack --disable-nas --disable-openal --disable-pulse --disable-blura
y --disable-smb --disable-fribidi --disable-cdparanoia --disable-ladspa --disabl
e-liblzo --disable-win32dll --disable-qtx --disable-real --disable-libopencore_a
mrnb --disable-libopencore_amrwb --disable-libgsm --disable-tv-v4l1 --disable-tv
-v4l2 --disable-librtmp --disable-mng --enable-ass --enable-ass-internal --disab
le-enca --disable-dga1 --disable-dga2 --disable-gl --disable-xinerama --disable-
vm --disable-rtc --disable-arts --disable-caca --disable-lirc --disable-sdl --di
sable-svga --disable-aa --disable-esd --disable-joystick --x-libraries=/usr/loca
l/lib --x-includes=/usr/local/include --prefix=/usr/local --mandir=/usr/local/ma
n --build=amd64-portbld-freebsd8.2

And, there is no -pthread in this file.

 I'll look into your patch set as soon as I can!
 Until then, thanks for testing and patching!

 Best regards
 Riggs



-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: CFT: mplayer and mencoder updates

[Zhihao Yuan]

Hi:

Could you take a look at this (support FreeBSD OSS 24-bit output)?

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/156747

I unified the some patches here:

https://gist.github.com/1362097

1. Disable ALSA explicitly;
2. Allow internal libass if ASS is tuned off;
3. OSS 24-bit output;
4. FreeBSD's log2  log2f in libc.

Let me test the port...

stable/8:

gcc:

ffmpeg/libavformat/libavformat.a(udp.o): In function `udp_open':
udp.c:(.text+0xf8e): undefined reference to `pthread_create'
ffmpeg/libavcodec/libavcodec.a(pthread.o): In function `ff_thread_init':
pthread.c:(.text+0x178c): undefined reference to `pthread_create'
pthread.c:(.text+0x1894): undefined reference to `pthread_create'
collect2: ld returned 1 exit status

clang:

clang: warning: argument unused during compilation:
'-rpath=/usr/lib:/usr/local/lib'
ffmpeg/libavformat/libavformat.a(udp.o): In function `udp_open':
libavformat/udp.c:(.text+0x907): undefined reference to `pthread_create'
ffmpeg/libavcodec/libavcodec.a(pthread.o): In function `ff_thread_init':
libavcodec/pthread.c:(.text+0xded): undefined reference to `pthread_create'
libavcodec/pthread.c:(.text+0x104e): undefined reference to `pthread_create'
clang: error: linker command failed with exit code 1 (use -v to see invocation)

The original config.mak has no -pthread, so the replacement in
port-configure fails to work.

The program works fine. Thanks.

On Mon, Dec 19, 2011 at 4:35 PM, Thomas Zander
thomas.e.zan...@googlemail.com wrote:
 Hi list,

 on http://www.rrr.de/~riggs/mplayer/m20111219.tar.bz2 you can find the
 draft of updates to the mplayer and mencoder ports.

 Please have a look, play with it and let me know what you think.
 I tested it on 8.2 STABLE i386 and amd64 only so far, so I hope it
 works for 9 and 10 as well.

 As always, comments, suggestions and especially patches are more than welcome.

 Best regards
 Riggs
 ___
 freebsd-multime...@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia
 To unsubscribe, send any mail to freebsd-multimedia-unsubscr...@freebsd.org



-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Linux compatibility with more than one Linux installed?

[Zhihao Yuan]

On Tue, Dec 6, 2011 at 3:53 AM, Thomas Mueller
mueller6...@bellsouth.net wrote:
 The X server has a unix socket somewhere in /tmp. Normally this is used 
 instead of a TCP connection to the localhost. You need to change the DISPLAY
 env-variable to use a TCP connection, or you need o make the unix socket 
 available to the chrooted linux-env.

 The linuxulator in FreeBSD is nearly linux 2.6.16 compatible. We lack 
 inotify and epoll support which the 2.6.16 kernel normally supports. If your 
 system does
 not depend upon inotify, epoll and anything newer than 2.6.16, it should 
 work. If you give it a try, please report success or failure to
 emulat...@freebsd.org.

 Bye,
 Alexander.

 Now I might have something to try, but it is very unlikely that I would build 
 a Linux kernel = 2.6.16, especially with new hardware that might need the 
 latest drivers.  I will primarily want to run Linux natively rather than 
 under FreeBSD.

 I think emulators/linux_dist-gentoo-stage3 and 
 emulators/linux_base-gentoo-stage3 must use kernel far beyond 2.6.16.

 But I think, when chrooting into Linux from FreeBSD, FreeBSD kernel is the 
 one in effect.


Not really. The actual thing is, linuxulator is a Linux kernel running
as a FreeBSD kernel module. The only thing FreeBSD kernel do is to
identify the Linux program and to pass it to the Linux kernel. To the
Linux programs inside a GNU chroot enviroment, they think they are
running inside a Linux box and actually they are running inside a
Linux box. To the Linux programs running under a FreeBSD base, they
may identify that the base is not GNU by invoking some external
programs like `uname`. However, we can replace their sh with
/compat/linux/bin/sh, so that they are blind again.

 Tom

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


-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Linux compatibility with more than one Linux installed?

[Zhihao Yuan]

On Tue, Dec 6, 2011 at 6:21 AM, RW rwmailli...@googlemail.com wrote:
 On Tue, 6 Dec 2011 04:54:18 -0600
 Zhihao Yuan wrote:


 Not really. The actual thing is, linuxulator is a Linux kernel running
 as a FreeBSD kernel module. The only thing FreeBSD kernel do is to
 identify the Linux program and to pass it to the Linux kernel. To the
 Linux programs inside a GNU chroot enviroment, they think they are
 running inside a Linux box and actually they are running inside a
 Linux box.

 Are you sure about that? I was under the impression that it was a
 fairly thin emulation layer on top of the FreeBSD kernel. Has something
 changed?

To Linux program, there is no emulation layer. This technology
should be called extended ELF lookup table, and has nothing to do
with emulation.

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



-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Linux compatibility with more than one Linux installed?

[Zhihao Yuan]

On Tue, Dec 6, 2011 at 7:45 AM, RW rwmailli...@googlemail.com wrote:
 On Tue, 6 Dec 2011 06:29:03 -0600
 Zhihao Yuan wrote:

 On Tue, Dec 6, 2011 at 6:21 AM, RW rwmailli...@googlemail.com wrote:
  On Tue, 6 Dec 2011 04:54:18 -0600
  Zhihao Yuan wrote:
 
 
  Not really. The actual thing is, linuxulator is a Linux kernel
  running as a FreeBSD kernel module. The only thing FreeBSD kernel
  do is to identify the Linux program and to pass it to the Linux
  kernel. To the Linux programs inside a GNU chroot enviroment, they
  think they are running inside a Linux box and actually they are
  running inside a Linux box.
 
  Are you sure about that? I was under the impression that it was a
  fairly thin emulation layer on top of the FreeBSD kernel. Has
  something changed?

 To Linux program, there is no emulation layer. This technology
 should be called extended ELF lookup table, and has nothing to do
 with emulation.

 It's not emulation in the narrow sense that vmware is emulation and
 wine isn't, but it certainly is emulation within the normal sense or the
 word. My dictionary defines emulate as imitate zealously.

 But what I was getting at was the statement linuxulator is a Linux
 kernel running as a FreeBSD kernel module which I'm guessing now you
 didn't mean literally.

FreeBSD handbook:
http://www.freebsd.org/doc/handbook/linuxemu-advanced.html

In effect, there is a Linux kernel in the FreeBSD kernel; the various
underlying functions that implement all of the services provided by
the kernel are identical to both the FreeBSD system call table
entries, and the Linux system call table entries: file system
operations, virtual memory operations, signal delivery, System V IPC,
etc...

So, if you define a Linux kernel as every thing written by Linus and
his followers, then I'm wrong; but if you agree that Android is not
GNU but it does run a Linux kernel, then I'm probably right.

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



-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Linux compatibility with more than one Linux installed?

[Zhihao Yuan]

Well, I'm wrong. I read in effect as in fact...

--
Zhihao Yuan
On Dec 6, 2011 9:33 AM, RW rwmailli...@googlemail.com wrote:

 On Tue, 6 Dec 2011 08:04:59 -0600
 Zhihao Yuan wrote:

  On Tue, Dec 6, 2011 at 7:45 AM, RW rwmailli...@googlemail.com wrote:

   But what I was getting at was the statement linuxulator is a Linux
   kernel running as a FreeBSD kernel module which I'm guessing now
   you didn't mean literally.
 
  FreeBSD handbook:
  http://www.freebsd.org/doc/handbook/linuxemu-advanced.html
 
  In effect, there is a Linux kernel in the FreeBSD kernel; ...

 Clearly the author of that article doesn't agree with you or he
 wouldn't have written In effect. If your statement had been:
 linuxulator is effectively a Linux kernel running as a FreeBSD
 kernel, then it wouldn't have been plain wrong.

  So, if you define a Linux kernel as every thing written by Linus and
  his followers, then I'm wrong; but if you agree that Android is not
  GNU but it does run a Linux kernel, then I'm probably right.

 Android is based on fork of Linux, it contains real Linux code. All you
 could argue from that is that the linuxulator  could be called Linux if
 it were based on Linux code.

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

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

Re: Plan to add a bsd.pure.mk

[Zhihao Yuan]

On Mon, Dec 5, 2011 at 1:28 AM, Mark Linimon lini...@lonesome.com wrote:
 I would like to hold off on any more disruptive changes to the tree
 until we can get this release out the door.  If that means devel/clang
 needs to stay at its current value (and only clang-devel updated), then
 that's fine.

devel/clang always points to the release version, and its maintainer
is contacting other maintainers who has ports depends on clang/llvm to
fix the broken stuff.


 mcl



-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Plan to add a bsd.pure.mk

[Zhihao Yuan]

No, we don't need it that to upgrade llvm, but I need to decide soon.

--
Zhihao Yuan
On Dec 5, 2011 10:16 AM, Brooks Davis bro...@freebsd.org wrote:

 On Mon, Dec 05, 2011 at 01:28:33AM -0600, Mark Linimon wrote:
  I would like to hold off on any more disruptive changes to the tree
  until we can get this release out the door.  If that means devel/clang
  needs to stay at its current value (and only clang-devel updated), then
  that's fine.

 We don't actually need to add a bsd.pure.mk to upgrade llvm.  We would
 need to complete the repocopy in ports/163030 and change the build and
 run depends in lang/pure which would change the depends of the 12ish
 ports involved.  Similar changes are needed in a couple other ports.

 I'll leave it up to portmgr to decide if that's too disruptive.  IMO if
 any change of this scope (an upgrade triggering less than dozen rebuilds,
 mostly of ports that aren't widely used) should be approved, it should
 be this one given our general toolchain focus.

 -- Brooks

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

Re: Plan to add a bsd.pure.mk

[Zhihao Yuan]

portmgr@:

Clang 3.0 is released and about to replace the clang-2.9 in ports.
Pure 0.47 in ports does not build with 3.0, so I must make sure
ports/161799 can be committed soon. From now on, 18 hours. If I do not
get a response from portmgr@ with in 18 hours, I'll assume my request,
to add the bsd.pure.mk script into /usr/ports/Mk, is rejected. Thanks.

On Tue, Nov 15, 2011 at 4:35 PM, Zhihao Yuan lich...@gmail.com wrote:
 Currently, 12. Plus 3 committed, 1 unsubmitted, 3~4 planning to port. The
 total existing addons are listed here:

 http://code.google.com/p/pure-lang/wiki/Addons

 I probably not going to port all of them, but this list is growing.


 On Tue, Nov 15, 2011 at 3:36 PM, Ion-Mihai Tetcu ite...@freebsd.org wrote:

 On Thu, 10 Nov 2011 13:02:38 -0600
 Zhihao Yuan lich...@gmail.com wrote:

  Hi,
 
  The PR which updates all pure-* ports was passed to portmgr for a long
  time, since it seem that to put a
 
  .if defined(USE_PURE)
  .include ${PORTSDIR}/Mk/bsd.pure.mk
  .endif
 
  In bsd.port.mk may a be better choice. Though Pure is not as popular
  as some languages like PHP or Python, but it does and it will have
  more ports than like Go. To include bsd.pure.mk under Mk/ can lower 2
  lines in ~20 ports (or I have to leave it under lang/pure's private
  directory).

 How many pure ports are there ATM?

 --
 IOnut - Un^d^dregistered ;) FreeBSD user
  Intellectual Property is   nowhere near as valuable   as Intellect
 FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B




 --
 Zhihao Yuan, nickname lichray
 The best way to predict the future is to invent it.
 ___
 4BSD -- http://4bsd.biz/



-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Plan to add a bsd.pure.mk

[Zhihao Yuan]

Currently, 12. Plus 3 committed, 1 unsubmitted, 3~4 planning to port. The
total existing addons are listed here:

http://code.google.com/p/pure-lang/wiki/Addons

I probably not going to port all of them, but this list is growing.

On Tue, Nov 15, 2011 at 3:36 PM, Ion-Mihai Tetcu ite...@freebsd.org wrote:

 On Thu, 10 Nov 2011 13:02:38 -0600
 Zhihao Yuan lich...@gmail.com wrote:

  Hi,
 
  The PR which updates all pure-* ports was passed to portmgr for a long
  time, since it seem that to put a
 
  .if defined(USE_PURE)
  .include ${PORTSDIR}/Mk/bsd.pure.mk
  .endif
 
  In bsd.port.mk may a be better choice. Though Pure is not as popular
  as some languages like PHP or Python, but it does and it will have
  more ports than like Go. To include bsd.pure.mk under Mk/ can lower 2
  lines in ~20 ports (or I have to leave it under lang/pure's private
  directory).

 How many pure ports are there ATM?

 --
 IOnut - Un^d^dregistered ;) FreeBSD user
  Intellectual Property is   nowhere near as valuable   as Intellect
 FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B




-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Plan to add a bsd.pure.mk

[Zhihao Yuan]

Hi,

The PR which updates all pure-* ports was passed to portmgr for a long
time, since it seem that to put a

.if defined(USE_PURE)
.include ${PORTSDIR}/Mk/bsd.pure.mk
.endif

In bsd.port.mk may a be better choice. Though Pure is not as popular as
some languages like PHP or Python, but it does and it will have more ports
than like Go. To include bsd.pure.mk under Mk/ can lower 2 lines in ~20
ports (or I have to leave it under lang/pure's private directory).

I included both the .mk file, and the missing, new, pure-readline port
here. In bsd.pure.mk, we support user to specify the
pure-* dependencies through

USE_PURE= readline ffi

And readline is the one we have't inluded yet.

Btw, they are two more pure ports pending here

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/161800

Please commit they according to the way you accept bsd.pure.mk. Thanks.

-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/


bsd.pure.mk
Description: Binary data
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: CFT Chromium 15.0.874.92

[Zhihao Yuan]

Tested, no problem, with all acceleration + flash enabled. Thanks!

On Sun, Oct 16, 2011 at 9:41 AM, George Liaskos geo.lias...@gmail.comwrote:

 On Sun, Oct 16, 2011 at 5:34 PM, George Liaskos geo.lias...@gmail.com
 wrote:
  Hello,
 
  http://cybertron.gr/chromium-20111016.tar.xz
  http://cybertron.gr/chromium-15.0.874.92.tbz
 

 Meh, sorry about that. I pushed send by mistake.

 What i meant to write was : please test Chromium 15.0.874.92 :)

 There are many people that report problems with the current version of
 Chromium in ports.
 I believe that this revision of the port should resolve most of the
 issues but it would be really nice if we have more feadback.

 The package is for 9 amd64 compiled with gcc45.


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




-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: ImageMagick fails to build when upgrading.

[Zhihao Yuan]

On Wed, Oct 12, 2011 at 4:47 AM, Paul Macdonald p...@ifdnrg.com wrote:

 On 11/10/2011 11:58, Leslie Jensen wrote:



 /usr/ports/graphics/**ImageMagick/work/ImageMagick-**
 6.7.2-10/test-suite.log


  Segmentation fault (core dumped)


 in case you hadn't spotted 6.7.3.0 is in ports tree and builds ok for me.

 Paul.

 --
 -
 Paul Macdonald
 IFDNRG Ltd
 Web and video hosting
 -
 t: 0131 5548070
 m: 07534206249
 e: p...@ifdnrg.com
 w: http://www.ifdnrg.com
 -
 IFDNRG
 40 Maritime Street
 Edinburgh
 EH6 6SA
 -



 __**_
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/**mailman/listinfo/freebsd-portshttp://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to 
 freebsd-ports-unsubscribe@**freebsd.orgfreebsd-ports-unsubscr...@freebsd.org
 


I checked out the latest version in ports, but this test still fails for
gcc46. I'll try clang latter.

-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Vim does not build with ruby19 (since ruby19 does not install the ruby command)

[Zhihao Yuan]

Hi,

I specified RUBY_DEFAULT_VER=1.9 in /etc/make.conf, and rebuild everything
relates to ruby, and I found the successfully built Vim lacks of the ruby
support.

By default, vim requires the 'ruby' command when building WITH_RUBY=1, but
ruby19 does not install the command.

One solution is that to install the command as a symbol link, and mark
ruby-1.8 and ruby-1.9 as conflicts.

Another one only works for vim, to set the '--with-ruby-command=ruby19' as a
configure args.

Any comments?

-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Vim does not build with ruby19 (since ruby19 does not install the ruby command)

[Zhihao Yuan]

On Tue, Oct 11, 2011 at 1:36 PM, Ruslan Mahmatkhanov cvs-...@yandex.ruwrote:

 Zhihao Yuan wrote on 11.10.2011 17:56:

  Hi,

 I specified RUBY_DEFAULT_VER=1.9 in /etc/make.conf, and rebuild everything
 relates to ruby, and I found the successfully built Vim lacks of the ruby
 support.

 By default, vim requires the 'ruby' command when building WITH_RUBY=1, but
 ruby19 does not install the command.

 One solution is that to install the command as a symbol link, and mark
 ruby-1.8 and ruby-1.9 as conflicts.

 Another one only works for vim, to set the '--with-ruby-command=ruby19' as
 a
 configure args.

 Any comments?


 I'd check if we already have ${PREFIX}/bin/ruby, and if not - install
 symlink. If ${PREFIX}/bin/ruby is already there - install just ruby1X. This
 can be added to both ruby ports.

 --
 Regards,
 Ruslan

 Tinderboxing kills... the drives.


I suggest that to make the 'ruby' command obey the RUBY_DEFAULT_VER setting,
like what python ports do.

-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: TeXLive

[Zhihao Yuan]

Similar question. I tried to install the texlive-xetex. The installation is
successful, but there is no .fmt files installed.

On Sun, Oct 9, 2011 at 9:58 PM, Stephen Montgomery-Smith 
step...@missouri.edu wrote:

 Hey guys, I did


 make -C /usr/ports/ports-mgmt/**portshaker-config install
  # Ensure TEXLIVE is checked
 portshaker -v

 Now I have a whole bunch of texlive ports installed under /usr/ports/print.
  Am I just supposed to build the ports I need, or is there some grand
 texlive-build-all port that is in this long list somewhere?

 __**_
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/**mailman/listinfo/freebsd-portshttp://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to 
 freebsd-ports-unsubscribe@**freebsd.orgfreebsd-ports-unsubscr...@freebsd.org
 




-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: chromium 14.0.835.202 build error

[Zhihao Yuan]

Fixed, but not committed yet.
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/161323

On Thu, Oct 6, 2011 at 1:38 PM, Marco Beishuizen mb...@xs4all.nl wrote:

 Hi,

 Yesterday I portupgraded my ports. Chromium doesn't build with:

 ...
  CXX(target) out/Release/obj.target/**browser/chrome/browser/ui/**
 webui/print_preview_ui.o
 chrome/browser/ui/webui/print_**preview_handler.cc: In member function
 'void PrintSystemTaskProxy::**GetPrinterCapabilities(const std::string)':
 chrome/browser/ui/webui/print_**preview_handler.cc:291: error:
 'ppd_file_t' was not declared in this scope
 chrome/browser/ui/webui/print_**preview_handler.cc:291: error: 'ppd' was
 not declared in this scope
 chrome/browser/ui/webui/print_**preview_handler.cc:291: error:
 'ppdOpenFile' was not declared in this scope
 chrome/browser/ui/webui/print_**preview_handler.cc:293: error:
 'ppd_attr_t' was not declared in this scope
 chrome/browser/ui/webui/print_**preview_handler.cc:293: error: 'attr' was
 not declared in this scope
 chrome/browser/ui/webui/print_**preview_handler.cc:293: error:
 'ppdFindAttr' was not declared in this scope
 chrome/browser/ui/webui/print_**preview_handler.cc:297: error:
 'ppd_choice_t' was not declared in this scope
 chrome/browser/ui/webui/print_**preview_handler.cc:297: error: 'ch' was
 not declared in this scope
 chrome/browser/ui/webui/print_**preview_handler.cc:297: error:
 'ppdFindMarkedChoice' was not declared in this scope
 chrome/browser/ui/webui/print_**preview_handler.cc:299: error:
 'ppd_option_t' was not declared in this scope
 chrome/browser/ui/webui/print_**preview_handler.cc:299: error: 'option'
 was not declared in this scope
 chrome/browser/ui/webui/print_**preview_handler.cc:299: error:
 'ppdFindOption' was not declared in this scope
 chrome/browser/ui/webui/print_**preview_handler.cc:301: error:
 'ppdFindChoice' was not declared in this scope
 chrome/browser/ui/webui/print_**preview_handler.cc:307: error: 'ppdClose'
 was not declared in this scope
 gmake: *** 
 [out/Release/obj.target/**browser/chrome/browser/ui/**webui/print_preview_handler.o]
 Error 1
 gmake: *** Waiting for unfinished jobs
 *** Error code 1
 ...

 I've never seen this one before. Has anyone an idea? Running FreeBSD
 8.2-stable and portstree is up-to-date.

 Marco

 --
 The distinction between true and false appears to become
 increasingly blurred by... the pollution of the language.
-- Arne Tiselius
 __**_
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/**mailman/listinfo/freebsd-portshttp://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to 
 freebsd-ports-unsubscribe@**freebsd.orgfreebsd-ports-unsubscr...@freebsd.org
 




-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: FreeBSD Ports: sylpheed, gnash, seamonkey

[Zhihao Yuan]

It's updating to 3.1.1
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/158798
I guess this will be committed soon. Or you can just patch and try it earlier.

On Mon, Jul 25, 2011 at 4:25 PM, Torfinn Ingolfsen tin...@gmail.com wrote:
 Hello,

 On Wed, Jun 29, 2011 at 10:47 AM, Marco Alberoni m.alber...@cineca.it wrote:
 Hello everybody, I usually use the applications Sylpheed, Gnash and
 Seamonkey, and for all of them there the FreeBSD port is not synchronized
 with the latest available version: are there any problems for their upgrade?

 Sylpheed 3.1.1 was released on May 6th, 2011. And on July 1st, 2011
 Sylpheed 3.2beta1 was released.
 What are the current plans for upgrading the Sylpheed port (if any)?

 Have a nice day.
 --
 Regards,
 Torfinn Ingolfsen
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org




-- 
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Why so many versions of the port science/hdf?

[Zhihao Yuan]

On Wed, May 11, 2011 at 8:32 PM, Stephen Montgomery-Smith
step...@missouri.edu wrote:
 Stephen Montgomery-Smith wrote:

 Why are there three versions of science/hdf in the ports?

 This is causing problems for me when I try to build the port
 octave-forge.  As dependencies, it calls in the octave port (which
 currently defaults to hdf5), the cgnslib port (which uses hdf5-18), and
 the opendx port (which uses hdf).  All of these ports function perfectly
 well with hdf5.18, because all the different versions of hdf conflict
 with each other.

 If we could settle on using hdf5-18 throughout, that would be great.  (I
 currently maintain opendx, so that would be something I can fix.)

 Are there ports that need hdf but don't build with hdf5-18?

 Thanks, Stephen


 Well I feel pretty dumb.  Actually it is my port, opendx, that needs the
 original hdf port.  I forgot to enable WITH_HDF before testing it!

 Stephen


 Stephen

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


math/PDL only builds with hdf4. It detects hdf.h and libdf.a.

-- 
Zhihao Yuan
The best way to predict the future is to invent it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Ask maintainership of lang/p5-F77 and math/PDL

[Zhihao Yuan]

Hi,

perl@ is not a maintainer, but I still waited a month for my last
contribution to these two ports (they are related). Now I want to
maintain these two ports. PDL 2.4.9 is released, and I'm going to
spend some time on it.

Btw, if someone want to let me to do so, please apply the patch
included to p5-F77 at the same time. The patch fixes a tiny problem
(${FC} defaults to f77 on 7.0R, which is not trustful).

-- 
Zhihao Yuan
The best way to predict the future is to invent it.


p5-ExtUtils-F77-1.17_1.patch
Description: Binary data
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Ask for maintainership of lang/p5-F77 and math/PDL

[Zhihao Yuan]

Hi,

 perl@ is not a maintainer, but I still waited a month for my last
 contribution to these two ports (they are related). Now I want to
maintain these two ports. PDL 2.4.9 is released, and I'm going to
 spend some time on it.

 Btw, if someone want to let me to do so, please apply the patch
 included to p5-F77 at the same time. The patch fixes a tiny problem
 (${FC} defaults to f77 on 7.0R, which is not trustful).

-- 
Zhihao Yuan
The best way to predict the future is to invent it.


p5-ExtUtils-F77-1.17_1.patch
Description: Binary data
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

ports/156747: multimedia/mplayer: fix 24-bits OSS + some improvements

[Zhihao Yuan]

Hi,

 My final patches applies to mplayer and mencoder. After some
 discussion, I think they are stable enough. I hope someone can take
 this PR soon (before next upstream update, at least). Thanks so much.

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/156747

-- 
Zhihao Yuan
The best way to predict the future is to invent it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

ports/156747: multimedia/mplayer: fix 24-bits OSS + some improvements

[Zhihao Yuan]

Hi,

My final patches applies to mplayer and mencoder. After some
discussion, I think they are stable enough. I hope someone can take
this PR soon (before next upstream update, at least). Thanks so much.

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/156747

-- 
Zhihao Yuan
The best way to predict the future is to invent it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Dropping maintainership of my ports

[Zhihao Yuan]

On Tue, Apr 26, 2011 at 8:43 PM, Charlie Kester corky1...@comcast.net wrote:

 Well, due to some serious philosophical differences re these
 deprecation campaigns and what seems to be resistance to any further
 discussion, I don't think I can continue working with the committers.
 So I'm stepping down.

 If no one else wants to maintain them, please reset the maintainer of the
 following ports to po...@freebsd.org:

 audio/mcplay
 deskutils/osmo
 deskutils/teapot
 devel/argtable
 devel/egypt
 devel/gengetopt
 devel/libXGP
 devel/libYGP
 finance/xinvest
 finance/xquote
 graphics/box
 graphics/boxer
 graphics/fly
 graphics/sng
 math/ised
 misc/vifm
 misc/xsw
 multimedia/gpodder
 multimedia/openshot
 multimedia/photofilmstrip
 security/beecrypt
 security/ccrypt
 security/nettle
 security/ranpwd
 sysutils/dircomp
 sysutils/gaffitter
 sysutils/iextract
 sysutils/lookat
 sysutils/moreutils
 sysutils/moreutils-parallel
 sysutils/ncdu
 sysutils/rdup
 textproc/tdhkit
 x11/fbpanel

O-o-ok... philosophical differences.

audio/mcplay and the 3 multimedia-related ports, + fbpanel, have many
users, AFAIK, and require much works. We need to someone to take them
soon.



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




-- 
Zhihao Yuan
The best way to predict the future is to invent it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: graphics/simpleviewer doesn't build on head(?)

[Zhihao Yuan]

On Fri, Apr 8, 2011 at 12:55 AM, Sergey V. Dyatko
sergey.dya...@gmail.com wrote:
 Hi,

 I'm trying to build graphics/simpleviewerer and got following error:

 http://tiger.ipfw.ru/files/simpleviewer.txt

 tiger# uname -a
 FreeBSD tiger.minsk.domain 9.0-CURRENT FreeBSD 9.0-CURRENT #36 r220184:
 Thu Mar 31 16:17:14 EEST 2011
 root@tiger.minsk.domain:/usr/obj/usr/src/sys/tiger-desktop  i386


I tested it on 8-STABLE, and it does not build either (with gcc45).
The port maintainer add a strange section to post-patch:

@${REINPLACE_CMD} -e 's,const struct dirent,struct dirent,' \
${WRKSRC}/src/fileslist.*

Remove it, and it will works.

 --
 wbr, tiger

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


-- 
Zhihao Yuan
The best way to predict the future is to invent it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: graphics/simpleviewer doesn't build on head(?)

[Zhihao Yuan]

2011/4/8 Sergey V. Dyatko sergey.dya...@gmail.com:
 On Fri, 8 Apr 2011 01:36:46 -0500
 Zhihao Yuan lich...@gmail.com wrote:

 On Fri, Apr 8, 2011 at 12:55 AM, Sergey V. Dyatko
 sergey.dya...@gmail.com wrote:
  Hi,
 
  I'm trying to build graphics/simpleviewerer and got following error:
 
  http://tiger.ipfw.ru/files/simpleviewer.txt
 
  tiger# uname -a
  FreeBSD tiger.minsk.domain 9.0-CURRENT FreeBSD 9.0-CURRENT #36
  r220184: Thu Mar 31 16:17:14 EEST 2011
  root@tiger.minsk.domain:/usr/obj/usr/src/sys/tiger-desktop  i386
 

 I tested it on 8-STABLE, and it does not build either (with gcc45).
 The port maintainer add a strange section to post-patch:

       @${REINPLACE_CMD} -e 's,const struct dirent,struct dirent,' \
               ${WRKSRC}/src/fileslist.*

 Remove it, and it will works.

 Thanks for reply.
 I'm confused, maintainer commit fix for 'esc' key
 (PORTREVISION=  1).
 So I think port build fine for him :)

Whatever... I don't like this image viewer. Let others send PR or something.


  --
  wbr, tiger
 

 --
 wbr, tiger



-- 
Zhihao Yuan
The best way to predict the future is to invent it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: graphics/simpleviewer doesn't build on head(?)

[Zhihao Yuan]

2011/4/8 Alexey Dokuchaev da...@freebsd.org:
 On Fri, Apr 08, 2011 at 01:50:27AM -0500, Zhihao Yuan wrote:
 Whatever... I don't like this image viewer.

 While this viewer is far from perfect, I find that it at least works
 (contrary to gliv which dumps core on me both now and many years ago
 when I first discovered it) and performs scaling correctly (unlike pho,
 which is currently my viewer of choice).

 I'd happily switch to anything at least as good as default viewer in
 windoze xp, but have not seen anything decent so far.  Maybe you can
 recommend something which is not part of Gnome or KDE?

The reason I don't like it is, my ATI driver does not support OpenGL
very well -- when I scale the window size, the content disappears.

I use xli for years. When I need to see an image which is not
supported by xli (like GIF), I use display command (ImageMagick). When
I need to see a lot of images (like a manga), I use comix -- it has
some special display modes designed for manga or book.


 ./danfe


-- 
Zhihao Yuan
The best way to predict the future is to invent it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: graphics/simpleviewer doesn't build on head(?)

[Zhihao Yuan]

2011/4/8 Alexey Dokuchaev da...@freebsd.org:
 On Fri, Apr 08, 2011 at 02:22:17AM -0500, Zhihao Yuan wrote:
 2011/4/8 Alexey Dokuchaev da...@freebsd.org:
  On Fri, Apr 08, 2011 at 01:50:27AM -0500, Zhihao Yuan wrote:
  Whatever... I don't like this image viewer.
 
  I'd happily switch to anything at least as good as default viewer in
  windoze xp, but have not seen anything decent so far. Maybe you can
  recommend something which is not part of Gnome or KDE?

 The reason I don't like it is, my ATI driver does not support OpenGL
 very well -- when I scale the window size, the content disappears.

 Same bug here with Intel 915GM.  :-(

 I use xli for years. When I need to see an image which is not
 supported by xli (like GIF), I use display command (ImageMagick). When
 I need to see a lot of images (like a manga), I use comix -- it has
 some special display modes designed for manga or book.

 Unfortunately, graphics/xli seems to be deprecated and scheduled for
 termination after 2011-05-01.  Perhaps you'd like to become new
 maintainer?

Yes. So far, I only maintain new ports. How do I take managership of
other ports?


 ./danfe


-- 
Zhihao Yuan
The best way to predict the future is to invent it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: graphics/simpleviewer doesn't build on head(?)

[Zhihao Yuan]

2011/4/8 Alexey Dokuchaev da...@freebsd.org:
 On Fri, Apr 08, 2011 at 02:39:50AM -0500, Zhihao Yuan wrote:
 2011/4/8 Alexey Dokuchaev da...@freebsd.org:
  Unfortunately, graphics/xli seems to be deprecated and scheduled for
  termination after 2011-05-01. Perhaps you'd like to become new
  maintainer?

 Yes. So far, I only maintain new ports. How do I take managership of
 other ports?

 I will clean up graphics/xli and set you as maintainer.  Generally, you
 can post an email on this list@ or file a PR.  Maybe since just asking
 for maintainership is trivial change, spamming PR database is not needed.

 ./danfe


Thanks. The original distfile source can be removed. Others looks fine.

-- 
Zhihao Yuan
The best way to predict the future is to invent it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: graphics/simpleviewer doesn't build on head(?)

[Zhihao Yuan]

On Fri, Apr 8, 2011 at 2:59 AM, Zhihao Yuan lich...@gmail.com wrote:
 2011/4/8 Alexey Dokuchaev da...@freebsd.org:
 On Fri, Apr 08, 2011 at 02:39:50AM -0500, Zhihao Yuan wrote:
 2011/4/8 Alexey Dokuchaev da...@freebsd.org:
  Unfortunately, graphics/xli seems to be deprecated and scheduled for
  termination after 2011-05-01. Perhaps you'd like to become new
  maintainer?

 Yes. So far, I only maintain new ports. How do I take managership of
 other ports?

 I will clean up graphics/xli and set you as maintainer.  Generally, you
 can post an email on this list@ or file a PR.  Maybe since just asking
 for maintainership is trivial change, spamming PR database is not needed.

 ./danfe


 Thanks. The original distfile source can be removed. Others looks fine.

Oh. Btw. If you need to commit this port, please add a patch. It
eliminate many warnings when building xli.


 --
 Zhihao Yuan
 The best way to predict the future is to invent it.


-- 
Zhihao Yuan
The best way to predict the future is to invent it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: graphics/simpleviewer doesn't build on head(?)

[Zhihao Yuan]

2011/4/8 Alexey Dokuchaev da...@freebsd.org:
 On Fri, Apr 08, 2011 at 03:03:20AM -0500, Zhihao Yuan wrote:
 On Fri, Apr 8, 2011 at 2:59 AM, Zhihao Yuan lich...@gmail.com wrote:
  2011/4/8 Alexey Dokuchaev da...@freebsd.org:
  I will clean up graphics/xli and set you as maintainer.
 
  Thanks. The original distfile source can be removed. Others looks fine.

 Oh. Btw. If you need to commit this port, please add a patch. It
 eliminate many warnings when building xli.

 Done.  You might be interested to know that Debian has this package of
 version 1.17.0-20061110, which is newer than ours.  I didn't take liberty
 to update the port which I don't use however.

This snapshot fixed a problem relates to PBM.

I sent a PR to move to MASTER_SITE_DEBIAN:
http://www.freebsd.org/cgi/query-pr.cgi?pr=156272

So that the distfile of this snapshot is available.

BTW... Debian's 2000~line own xli patch set is really shocking. How
much time these guys spent on this...


 ./danfe


-- 
Zhihao Yuan
The best way to predict the future is to invent it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: graphics/simpleviewer doesn't build on head(?)

[Zhihao Yuan]

On Fri, Apr 8, 2011 at 9:10 AM, Alexey Shuvaev
shuv...@physik.uni-wuerzburg.de wrote:
 On Fri, Apr 08, 2011 at 07:07:02AM +, Alexey Dokuchaev wrote:
 On Fri, Apr 08, 2011 at 01:50:27AM -0500, Zhihao Yuan wrote:
  Whatever... I don't like this image viewer.

 While this viewer is far from perfect, I find that it at least works
 (contrary to gliv which dumps core on me both now and many years ago
 when I first discovered it) and performs scaling correctly (unlike pho,
 which is currently my viewer of choice).

 I'd happily switch to anything at least as good as default viewer in
 windoze xp, but have not seen anything decent so far.  Maybe you can
 recommend something which is not part of Gnome or KDE?

 graphics/geeqie, it uses gtk but not gnome

Check this out:
https://wiki.archlinux.org/index.php/Lightweight_Applications


 0.02$,
 Alexey.
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


-- 
Zhihao Yuan
The best way to predict the future is to invent it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Removing Cruft from the ports tree

[Zhihao Yuan]

 to standardize our WITH_*/WITHOUT_* flags instead of giving a
commonly use flags instruction.


 ---


    While I understand there might some minor part of the community
 that has a sentimental attachment to the blue-on-gray-on-blue
 configuration, and still others want to prematurely optimize, a simple
 workaround could be implemented. We can allow users to add their own
 ./configure arguments to the makefile. This serves the needs of the
 community while allowing us to deal with a simpler and more reliable
 ports system.

    Feel free to express your thoughts here. I would like to get this
 hashed out now so the process could occur on a later date(1).

 --
 Eitan Adler



 Thank you very much .

 Mehmet Erol Sanliturk
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


-- 
Zhihao Yuan
The best way to predict the future is to invent it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Firefox does not build with gcc45

[Zhihao Yuan]

Hi,

It seems that shlibsign keep crashes:

/home/lichray/temp/firefox/work/mozilla-2.0/obj-amd64-unknown-freebsd8.2/nss/shlibsign
-v -i 
/home/lichray/temp/firefox/work/mozilla-2.0/obj-amd64-unknown-freebsd8.2/security/manager/../../dist/lib/libfreebl3.so
moduleSpec configdir='' certPrefix='' keyPrefix='' secmod=''
flags=noCertDB, noModDB
Generate a DSA key pair ...
Library File: 
/home/lichray/temp/firefox/work/mozilla-2.0/obj-amd64-unknown-freebsd8.2/nss/freebl/FreeBSD_SINGLE_SHLIB/libfreebl3.so
376337 bytes
Check File: 
/home/lichray/temp/firefox/work/mozilla-2.0/obj-amd64-unknown-freebsd8.2/nss/freebl/FreeBSD_SINGLE_SHLIB/libfreebl3.chk
Link: libfreebl3.chk
  hash: 20 bytes
78 d7 55 ce 21 79 d2 ff 3e f2
e8 06 a7 20 5e 96 2b d3 4b db
  signature: 40 bytes
5a 7b a1 8a 63 79 bd aa ba b7
17 29 26 3f b2 a7 de 1c e8 c9
40 4e 36 5e 48 e5 60 32 15 d5
d7 39 96 5f 96 2c 52 a2 61 d9
Segmentation fault (core dumped)
gmake[6]: *** 
[/home/lichray/temp/firefox/work/mozilla-2.0/obj-amd64-unknown-freebsd8.2/security/manager/../../dist/lib/libfreebl3.chk
gmake[6]: Leaving directory
`/home/lichray/temp/firefox/work/mozilla-2.0/security/nss/cmd/shlibsign'
...

The error is the same when I build it under /usr/ports/www.
When I issue the last command by hand, it seems that there is no
crash. But the core file does belong to shlibsign:
./obj-amd64-unknown-freebsd8.2/dist/lib/shlibsign.core

-- 
Zhihao Yuan
The best way to predict the future is to invent it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Building for libofa-0.9.3_6 fails

[Zhihao Yuan]

On Fri, Mar 25, 2011 at 5:56 PM, Heino Tiedemann
rotkaps_spam_t...@gmx.de wrote:
 Alex Dupre a...@freebsd.org wrote:

 Leslie Jensen ha scritto:
 I got this problem with building libofa-0.9.3_6

 What can I do to solve it?

 Set:

 CPPFLAGS+=    -I${LOCALBASE}/include

 in the port's Makefile.

 shouldn't it be put into that file by maintainer?

It should.


 Heino

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


-- 
Zhihao Yuan
The best way to predict the future is to invent it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: [HEADS UP] Ports Infrastructure Changes

[Zhihao Yuan]

On Sat, Mar 19, 2011 at 5:29 PM, Henk van Oers h...@signature.nl wrote:

 From: Pav Lucistnik p...@freebsd.org

 Matthias Andree pí¹e v so 19. 03. 2011 v 09:52 +0100:
 [...]

 Where do you see the dividing line between web apps on one hand and on
 the other hand http servers ... everything related to apache?  IOW,
 how do I decide if I put a new port into www-webapps or into www-servers
 for its primary category?

 Basically, everything that serves network is server and everything
 that generates pages on these servers is webapp.

 So: why is p5-Mojolicious in webapp, it serves network (main deployment).
 And it's a client too...

Not just p5-Mojolicious. Many webapps can be web servers, like Flask.
Even some unrelated packages can be www servers, like python, with
SimpleHTTPServer. And some www-clients can also be www-servers. For
example, opera. It's a client, server, email client, HTML-editor. You
can't just *separate* things into clients, servers, apps, and misc.

And also, during the development of the HTML5, there will be more and
more www-client ports can be used as servers, by using web socket. The
border of clients and servers will become fuzzy. We should not used a
C/S model to sort these ports.

That's why I suggest that to create a www-devel branch - you can
determined what a software is mainly designed for, but you can not
always determined what a software can be used as.


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


-- 
Zhihao Yuan
The best way to predict the future is to invent it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: [HEADS UP] Ports Infrastructure Changes

[Zhihao Yuan]

On Sat, Mar 19, 2011 at 5:29 PM, Henk van Oers h...@signature.nl wrote:

 From: Pav Lucistnik p...@freebsd.org

 Matthias Andree pí¹e v so 19. 03. 2011 v 09:52 +0100:
 [...]

 Where do you see the dividing line between web apps on one hand and on
 the other hand http servers ... everything related to apache?  IOW,
 how do I decide if I put a new port into www-webapps or into www-servers
 for its primary category?

 Basically, everything that serves network is server and everything
 that generates pages on these servers is webapp.

 So: why is p5-Mojolicious in webapp, it serves network (main deployment).
 And it's a client too...

My suggestion: separate www into www and www-devel. C/S model can not
clarify the developing web technology these years.


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


-- 
Zhihao Yuan
The best way to predict the future is to invent it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: [HEADS UP] Ports Infrastructure Changes

[Zhihao Yuan]

On Fri, Mar 18, 2011 at 9:32 PM, Michal Varga varga.mic...@gmail.com wrote:
 On Sat, 2011-03-19 at 09:49 +0800, Martin Wilke wrote:

 Attached is a proposed list of ports being moved from the www category.
 Please review, discuss and report ommissions and mistakes. The general
 key to the new categories is as follows:

 [...]

 www-webapps - web apps, frameworks, libraries

 Just a quick thought to the 'discuss' part: Is this (above) really the
 best name possible?

 I mean world wide web-webapps sounds kind of redundant.

 m.

www-devel may be preferred, since www-webapps contains the web frameworks, libs.
or may be devel-www :)


 --
 Michal Varga,
 Stonehenge (Gmail account)


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




-- 
Zhihao Yuan
The best way to predict the future is to invent it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Firefox 4 - Beta

[Zhihao Yuan]

On Mon, Mar 7, 2011 at 12:09 PM, Heino Tiedemann
rotkaps_spam_t...@gmx.de wrote:
 Sergey Nikolenko s...@swa.org.ru wrote:

 On 06.03.2011 19:17, Heino Tiedemann wrote:

 is there someone who likes to go for the Firefox 4 in ports?

 maybe into www/firefox-devel?


 Firefox 4 is in the State beta 12 - what means it is the release
 candidate.

 Firefox 4 is available for FreeBSD for a long time in our development
 repository. Please have a look at this page for more information about
 the freebsd-gecko repository:
 https://trillian.chruetertee.ch/freebsd-gecko/

 Firefox 4 lives at:
 https://trillian.chruetertee.ch/svn/freebsd-gecko/branches/experimental/www/firefox-devel/

 We are not going to commit a Firefox 4 Beta or RC to the ports tree. If
 you like to test Firefox 4 use the one from the development repository
 at your own risk.

 Cool.

 Any manpage or howto how I can gat this on my computer? Do I need SVN
 for that

 1. cd /usr/ports/devel/subversion; make install clean
 2. cd /usr/ports/www
 3. svn co
 https://trillian.chruetertee.ch/svn/freebsd-gecko/branches/experimental/www/firefox-devel
 4. cd firefox-devel
 5. make install clean

 The performance of Firefox 4 is impressive, sometimes it's even
 working faster than Chromium.

 Yes, it is Fast! I belive it is even faster on startup...

 One Question:

 Do I HAVE TO put it into my ports tree? Or can I put it somewhere into
 my home directory tree?

 e.g.
 1 cd ~/myports/www
 2 svn co 
 https://trillian.chruetertee.ch/svn/freebsd-gecko/branches/experimental/www/firefox-devel
 3 cd firefox-devel
 4 make install clean


 Does that work? Where doesthe distfile go to then?

distfiles goes to /usr/ports/distfiles. You don't have to mv it into
your ports tree. After you have done sudo make fetch, you can build
the port as a normal user.


 Heino

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


-- 
Zhihao Yuan
The best way to predict the future is to invent it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org