Re: games/supertux fails to start.

[David DEMELIER]

2010/4/20 Demelier David :
> Hi freebsd-ports@,
>
>   On my 8.0-STABLE amd64 games/supertux just fails to start.
>
>   Couldn't read /proc/self/exe, using default path: /usr/local/share/supertux
>   Datadir: /usr/local/share/supertux
>   Warning: No joysticks are available.
>
>   Error: Couldn't load musicfile
>   /usr/local/share/supertux/music/SALCON.MOD
>
>   zsh: abort (core dumped)  supertux
>
>   Is it same for you ?
>

I think it solved by the audio/sdl_mixer fix.

-- 
Demelier David
___
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: mplayer needs libcdio and libcdio isn't depending on

[David DEMELIER]

2010/4/21 Sahil Tandon :
> On Mon, 19 Apr 2010, Demelier David wrote:
>
>> When you install mplayer with libcdio support, if will build and
>> install it, but libcdio has no depend and could be detected as leaf
>> package. Then pkg_cleanup will ask you to remove it and if you remove
>> it you canno't use mplayer anymore if it needs this lib.
>>
>> Is that behavior expected ? I means that libcdio shouldn't be needed
>> by mplayer after the installation.
>
> I am not a user of multimedia/mplayer, but it seems that you believe
> sysutils/libcdio is required to *run* mplayer, whereas it is only listed
> as a *build* dependency.  Is that a correct summary of your report?
>

Yes but it's needed as *run* dependency, remove it and try to play
cd/dvd and every cdio related stuff, mplayer will fails on checking
shared libraries libcdio..

Cheers.

-- 
Demelier David
___
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"

net/ekiga3 plist failure ?

[David DEMELIER]

Hi freebsd-ports,

I just installed ekiga and tried to pkg_delete it, there is a lot of
output when removing it.

$ sudo pkg_delete ekiga3-3.2.6_2
Password:
pkg_delete: file '/usr/local/lib/locale/zh_TW/LC_MESSAGES' doesn't exist
pkg_delete: unable to completely remove directory
'/usr/local/lib/locale/zh_TW/LC_MESSAGES'
pkg_delete: file '/usr/local/lib/locale/zh_TW' doesn't exist
pkg_delete: unable to completely remove directory '/usr/local/lib/locale/zh_TW'
pkg_delete: file '/usr/local/lib/locale/zh_HK/LC_MESSAGES' doesn't exist
pkg_delete: unable to completely remove directory
'/usr/local/lib/locale/zh_HK/LC_MESSAGES'
pkg_delete: file '/usr/local/lib/locale/zh_HK' doesn't exist
pkg_delete: unable to completely remove directory '/usr/local/lib/locale/zh_HK'
pkg_delete: file '/usr/local/lib/locale/zh_CN/LC_MESSAGES' doesn't exist
pkg_delete: unable to completely remove directory
'/usr/local/lib/locale/zh_CN/LC_MESSAGES'
pkg_delete: file '/usr/local/lib/locale/zh_CN' doesn't exist
pkg_delete: unable to completely remove directory '/usr/local/lib/locale/zh_CN'
pkg_delete: file '/usr/local/lib/locale/xh/LC_MESSAGES' doesn't exist
pkg_delete: unable to completely remove directory
'/usr/local/lib/locale/xh/LC_MESSAGES'
pkg_delete: file '/usr/local/lib/locale/xh' doesn't exist
pkg_delete: unable to completely remove directory '/usr/local/lib/locale/xh'
pkg_delete: file '/usr/local/lib/locale/wa/LC_MESSAGES' doesn't exist
pkg_delete: unable to completely remove directory
'/usr/local/lib/locale/wa/LC_MESSAGES'
pkg_delete: file '/usr/local/lib/locale/wa' doesn't exist
pkg_delete: unable to completely remove directory '/usr/local/lib/locale/wa'
pkg_delete: file '/usr/local/lib/locale/vi/LC_MESSAGES' doesn't exist
pkg_delete: unable to completely remove directory
'/usr/local/lib/locale/vi/LC_MESSAGES'
pkg_delete: file '/usr/local/lib/locale/vi' doesn't exist
pkg_delete: unable to completely remove directory '/usr/local/lib/locale/vi'
pkg_delete: file '/usr/local/lib/locale/uk/LC_MESSAGES' doesn't exist
pkg_delete: unable to completely remove directory
'/usr/local/lib/locale/uk/LC_MESSAGES'
pkg_delete: file '/usr/local/lib/locale/uk' doesn't exist
pkg_delete: unable to completely remove directory '/usr/local/lib/locale/uk'
pkg_delete: file '/usr/local/lib/locale/tr/LC_MESSAGES' doesn't exist
pkg_delete: unable to completely remove directory
'/usr/local/lib/locale/tr/LC_MESSAGES'
pkg_delete: file '/usr/local/lib/locale/tr' doesn't exist
pkg_delete: unable to completely remove directory '/usr/local/lib/locale/tr'
pkg_delete: file '/usr/local/lib/locale/th/LC_MESSAGES' doesn't exist
pkg_delete: unable to completely remove directory
'/usr/local/lib/locale/th/LC_MESSAGES'
pkg_delete: file '/usr/local/lib/locale/th' doesn't exist
pkg_delete: unable to completely remove directory '/usr/local/lib/locale/th'
pkg_delete: file '/usr/local/lib/locale/te/LC_MESSAGES' doesn't exist
pkg_delete: unable to completely remove directory
'/usr/local/lib/locale/te/LC_MESSAGES'
pkg_delete: file '/usr/local/lib/locale/te' doesn't exist
pkg_delete: unable to completely remove directory '/usr/local/lib/locale/te'
pkg_delete: file '/usr/local/lib/locale/ta/LC_MESSAGES' doesn't exist
pkg_delete: unable to completely remove directory
'/usr/local/lib/locale/ta/LC_MESSAGES'
pkg_delete: file '/usr/local/lib/locale/ta' doesn't exist
pkg_delete: unable to completely remove directory '/usr/local/lib/locale/ta'
pkg_delete: file '/usr/local/lib/locale/sv/LC_MESSAGES' doesn't exist
pkg_delete: unable to completely remove directory
'/usr/local/lib/locale/sv/LC_MESSAGES'
pkg_delete: file '/usr/local/lib/locale/sv' doesn't exist
pkg_delete: unable to completely remove directory '/usr/local/lib/locale/sv'
pkg_delete: file '/usr/local/lib/locale/s...@latin/LC_MESSAGES' doesn't exist
pkg_delete: unable to completely remove directory
'/usr/local/lib/locale/s...@latin/LC_MESSAGES'
pkg_delete: file '/usr/local/lib/locale/s...@latin' doesn't exist
pkg_delete: unable to completely remove directory
'/usr/local/lib/locale/s...@latin'
pkg_delete: file '/usr/local/lib/locale/sr/LC_MESSAGES' doesn't exist
pkg_delete: unable to completely remove directory
'/usr/local/lib/locale/sr/LC_MESSAGES'
pkg_delete: file '/usr/local/lib/locale/sr' doesn't exist
pkg_delete: unable to completely remove directory '/usr/local/lib/locale/sr'
pkg_delete: file '/usr/local/lib/locale/sq/LC_MESSAGES' doesn't exist
pkg_delete: unable to completely remove directory
'/usr/local/lib/locale/sq/LC_MESSAGES'
pkg_delete: file '/usr/local/lib/locale/sq' doesn't exist
pkg_delete: unable to completely remove directory '/usr/local/lib/locale/sq'
pkg_delete: file '/usr/local/lib/locale/sl/LC_MESSAGES' doesn't exist
pkg_delete: unable to completely remove directory
'/usr/local/lib/locale/sl/LC_MESSAGES'
pkg_delete: file '/usr/local/lib/locale/sl' doesn't exist
pkg_delete: unable to completely remove directory '/usr/local/lib/locale/sl'
pkg_delete: file '/usr/local/lib/locale/sk/LC_MESSAGES' doesn't exist

python can't make package.

[David DEMELIER]

Hi freebsd-ports,

This morning I wasn't able to make package in lang/python26 port.

===>  Building package for python26-2.6.4
Creating package /usr/ports/packages/All/python26-2.6.4.tbz
Registering depends:.
Creating bzip'd tar ball in '/usr/ports/packages/All/python26-2.6.4.tbz'
tar: lib/python2.6/lib-dynload/_multiprocessing.so: Cannot stat: No
such file or directory
tar: Error exit delayed from previous errors.
pkg_create: make_dist: tar command failed with code 256
*** Error code 1

Stop in /usr/ports/lang/python26.
*** Error code 1

Stop in /usr/ports/lang/python26.

Is it a broken PLIST issue?

Cheers.

-- 
Demelier David
___
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: Status of Xorg 7.5 and xfce4?

[David DEMELIER]

2010/5/5 Richard Kuhns :
> On 05/05/10 10:26, Ondrej Majerech wrote:
>> Richard Kuhns wrote:
>>> I'll try renaming ~/.config/xfce4 when I get home this evening. I've already
>>> removed ~/.config/xfce4-session to no effect, and I don't have an xorg.conf 
>>> file
>>> at all.
>>
>> Then I suppose you are using HAL and Dbus, right? Does any of these two
>> complain about anything? You could try disabling them and writing an
>> Xorg.conf by hand and see that gets you anywhere.
>>
>
> Yes, I'm using HAL and Dbus. I'm getting the following error when I try to 
> start
> my desktop with xfce4-session installed (which, except for the process ID, is
> just like the other failure reports I've found in the mailing list archives):
> ===
> process 1675: arguments to dbus_message_new_signal() were incorrect, assertion
> "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1165.
> This is normally a bug in some application using the D-Bus library.
>  D-Bus not compiled with backtrace support so unable to print a backtrace
>
> (xfce4-settings-helper:1693): libxfcegui4-WARNING **: ICE I/O Error
>
> (xfce4-settings-helper:1693): xfce4-settings-helper-WARNING **: Failed to
> connect to session manager
> Abort trap (core dumped)
> xfce4-settings-helper is already running
>
> (xfce4-settings-helper:1699): libxfcegui4-WARNING **: ICE I/O Error
>
> (xfce4-settings-helper:1699): libxfcegui4-WARNING **: Disconnected from 
> session
> manager.
>
> (xfdesktop:1689): libxfcegui4-WARNING **: ICE I/O Error
> ===
>
> I've deinstalled and reinstalled libICE and all xfce4 ports since updating 
> Xorg.
>
>>>
>>> BTW, the machine I updated is running amd64; was your successful update 
>>> amd64 or
>>> i386?
>>
>> Mine's i386.
>
> OK, a general question then: could anyone running an FreeBSD 8.0 amd64
> kernel/userland report that they have a working Xorg 7.5/xfce4 installation?
>

Same for me, can't run xfce4 on amd64.

-- 
Demelier David
___
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: x11-wm/obconf segfaults

[David DEMELIER]

2010/5/12 Yuri Pankov :
> On Wed, May 12, 2010 at 04:21:35PM +0200, Demelier David wrote:
>> Hi freebsd-ports@,
>>
>>    Today I wanted to try x11-wm/openbox and its configuration manager called
>>    obconf found in x11-wm/obconf. I started it and it just segfaults :
>>
>>    (obconf:30154): Gtk-WARNING **: GtkSpinButton: setting an adjustment with 
>> non-zero page size is deprecated
>>    (no debugging symbols found)...
>>    Program received signal SIGSEGV, Segmentation fault.
>>    [Switching to Thread 804e041c0 (LWP 100235)]
>>    0x000800f4ee75 in g_object_type_init () from 
>> /usr/X11R6/lib/libgobject-2.0.so.0
>>
>>    King regards.
>>
>> --
>> Demelier David
>
> Check ports/146523 for a (possible) fix.
>

The patch worked for me, if it works we can commit it?


-- 
Demelier David
___
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-mgmt/portmaster does not have zsh completions anymore ?

[David DEMELIER]

Hi,

Today I upgraded the portmaster port to 2.27 and I noticed that there
was no completion anymore with my zsh. I was using it like portmaster
- where tab gave me all the options available, I was able to do
portmaster  to use portsdir pattern too. Now there is nothing !

Are these completions completely removed?

Cheers.

-- 
Demelier David
___
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: ports-mgmt/portmaster does not have zsh completions anymore ?

[David DEMELIER]

2010/5/19 Anonymous :
> Demelier David  writes:
>
>> On Wed, May 19, 2010 at 10:27:35AM -0700, Doug Barton wrote:
>>> The user reports in private e-mail that the completions file is installed, 
>>> but it's still not working. Can a zsh user help him out?
>>>
>>
>> Yes, sorry I forgot everytime to answer to all...
>
> Hmm, does following help?
>
>    $ autoload -Uz compinit
>    $ compinit
>
> You may want to run compinstall, though. See also zshcompsys(1).
>

mark...@melon ~ $ sudo portmaster -
22:59
No results for `arguments' or `file'

I never needed to work with zshcompsys, that's weird.

-- 
Demelier David
___
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: ports-mgmt/portmaster does not have zsh completions anymore ?

[David DEMELIER]

2010/5/19 Doug Barton :
> On 05/19/10 14:00, David DEMELIER wrote:
>>
>> mark...@melon ~ $ sudo portmaster -
>
> Try just:
> portmaster -
>
> Also, see the portmaster man page about setting up PM_SU_CMD.
>

I guess I'm the problem, I tested with a empty .zshrc and it works.
Sorry for the noise.

-- 
Demelier David
___
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"

Users and groups kept after a port deinstallation

[David DEMELIER]

Hi,

I used pkgsrc for a while on NetBSD. I was used to the pkgsrc
notifications about the users and groups leaves, when some ports are
removed these leaves are not used anymore. e.g pulseaudio needs some
users on the system.

Then the pkgsrc framework says to the user that are some users not
used anymore and they could remove them safely.

Ports has the lack of this kind of notification, that's why I would
start writing a patch in the ports infrastructure, or maybe someone
already proposed something else ?

I apologize for my bad english.

King regards.

-- 
Demelier David
___
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: Users and groups kept after a port deinstallation

[David DEMELIER]

2010/5/22 Garrett Cooper :
> On Fri, May 21, 2010 at 4:53 PM, RW  wrote:
>> On Fri, 21 May 2010 16:23:18 +0100
>> Florent Thoumie  wrote:
>>
>>> On Fri, May 21, 2010 at 11:11 AM, David DEMELIER
>>>  wrote:
>>> > Hi,
>>> >
>>> > I used pkgsrc for a while on NetBSD. I was used to the pkgsrc
>>> > notifications about the users and groups leaves, when some ports are
>>> > removed these leaves are not used anymore. e.g pulseaudio needs some
>>> > users on the system.
>>> >
>>>
>>> This was discussed in the following bug-report:
>>>
>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=108514
>>>
>>> I think the proper solution is to create a +UGIDS file to be able to
>>> maintain a refcount, but the status quo isn't that bad.
>>
>> Personally I'd much prefer to keep them so ls -l, filemanagers etc can
>> continue to use names rather than numbers for any files left behind.
>>
>> IMO the status quo is better than any solution that involves automated
>> deletion.
>
>I agree by and large with RW, but it would be nice if there was an
> audit tool to do this check and suggest whether or not a group should
> be added or removed in general, regardless of whether or not a
> pkg/port was added or removed.
> Thanks,
> -Garrett

Yes, of course I would not have something that remove automatically
without prompting the user. I just wanted something like :

Warning : these users are no long used by the system, you can remove then safely

user1, user2 etc

Cheers.
___
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"

x11/slim and /etc/login.conf

[David DEMELIER]

Hi freebsd-ports@,

Since slim do not use login(1) to log your user in, everything set in
/etc/login.conf won't be present on your session. If you did set some
settings they won't appear.

in the /usr/local/etc/slim.conf you can see :

login_cmd   exec /bin/sh - ~/.xinitrc %session

As described in the sh(1) manpage, the dash after the /bin/sh should
be a login shell, but it does not work. I'm guessing if we can do some
hack to make the /etc/login.conf used by slim.

If you have any ideas, just tell me !

Cheers.

-- 
Demelier David
___
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: Port request

[David DEMELIER]

2010/5/26 Matthias Andree :
> Am 26.05.2010 14:19, schrieb Jesse Smith:
>> I was told that requests for new ports should be submitted here. There's
>> one tool which I would like to see brought into the Ports system and
>> that's Network Manager
>> (http://fedoraproject.org/wiki/Tools/NetworkManager)
>>
>> It's the only networking tool I've found so far which will properly
>> handle my Novatel mobile modem and I would really like to be able to
>> make use of the modem while running FreeBSD.
>
> Hi Jesse,
>
> Network Manager (NM) will just automate steps you can do with other means, 
> too.
> It is not doing magic of any kind, and chances are your modem needs firmware
> that is available for Linux but not for FreeBSD, but I know nothing about your
> Novatel device.
>
> Regarding a FreeBSD port:
>
> (a) NM needs major porting efforts, and is an open, non-trivial, project of 
> the
> GNOME team, see 
>
> (b) I personally find that NM is an abomination that - particularly on 
> Laptops -
> causes more problems than it could possibly solve for me.
>    I routinely deinstall NetworkManager from openSUSE, Fedora, and Ubuntu 
> Linux
> distributions, because it frequently fails to configure WPA2-Enterprise with
> EAP-TLS or EAP-TTLS, fails to detect online state (making several applications
> start in offline mode or refuse to even attempt to connect), fails to 
> configure
> hidden 802.11 (WiFi/WLAN) networks, and causes other artifacts I don't have
> without NM.
>
> I'd personally also say Network Manager needs upstream bugfixing much more 
> than
> a port. Haven't tried Fedora 13 "Goddard" yet though.
>

I agree, personally I would prefer a wpa_supplicant / dhclient
graphical user interface instead of the sucky NetworkManager. For the
moment there is sysutils/wifimgr iirc but it's a quite unstable.

wpa_supplicant does everything, scanning for access points
automatically even you don't have X running, all WPA means of
associations, it's just perfect.

-- 
Demelier David
___
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"

games/wesnoth not localized ?

[David DEMELIER]

Hi,

I can't change the language in Wesnoth. They are shown but you can't
click on (they are not-clickable).

The messages files are installed : pkg_info -L wesnoth\*

[...]
/usr/local/share/locale/zh_TW/LC_MESSAGES/wesnoth-l.mo
/usr/local/share/locale/zh_TW/LC_MESSAGES/wesnoth-lib.mo
/usr/local/share/locale/zh_TW/LC_MESSAGES/wesnoth-low.mo
[...]

And the NLS option is defined :

mark...@melon /usr/ports/games/wesnoth $ make showconfig
===> The following configuration options are available for wesnoth-1.6.5_4:
 CAMPAIGN=on "Enable campaign server"
 EDITOR=on "Enable map editor"
 FRIBIDI=on "Enable bidirectional support"
 NLS=on "Enable localization"
 SERVER=on "Enable server"
 TOOLS=on "Enable extra tools for artists and translators"
===> Use 'make config' to modify these settings

Could it be a internal wesnoth problem ?

King regards.

-- 
Demelier David
___
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"

pidgin crashes everytime

[David DEMELIER]

Hi,

I recently updated pidgin to 2.7.1 and it crashes everytime now. I
started it with gdb and this is what happened just before it crashes :

Program received signal SIGBUS, Bus error.
[Switching to Thread 8058041c0 (LWP 100214)]
0x0008087996bc in msn_dc_listen_socket_created_cb (listenfd=21,
data=Variable "data" is not available.
)
at directconn.c:1009
1009directconn.c: No such file or directory.
in directconn.c

Anyone is having the same trouble?

Kind regards.

-- 
Demelier David
___
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"

Yet another segf with audio/sound-juicer

[David DEMELIER]

Hi,

I guess I don't have chance with FreeBSD, one of four applications I
install segfault. Now it's the time to sound-juicer.

Melon ~ $ gdb sound-juicer
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd"...(no debugging
symbols found)...
(gdb) run
Starting program: /usr/local/bin/sound-juicer
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...[New LWP
100263]
[New Thread 806c041c0 (LWP 100263)]
Gtk-Message: Failed to load module "gnomebreakpad": Shared object
"libgnomebreakpad.so" not found, required by "sound-juicer"
[New Thread 80a807100 (LWP 100268)]
[New Thread 80a806f40 (LWP 100269)]
[Thread 80a806f40 (LWP 100269) exited]
[New Thread 80a806bc0 (LWP 100269)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 806c041c0 (LWP 100263)]
0x004116c1 in on_delete_event ()

(gdb) bt
#0  0x004116c1 in on_delete_event ()
#1  0x004143eb in main ()

I hope it's a sound-juicer problem and not FreeBSD :-).

Kind regards.

-- 
Demelier David
___
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"

New pkg-message[.in] guideline idea

[David DEMELIER]

Hi freebsd-ports@,

I would like to propose you something that I would like to be done.
It's a cosmetic, useless thing but I like when things are made
homogeneously. That is the problem : as you can see, sometimes port
tells a message to the user but some maintainers used delimiters to
begin/end the message such as a lot of "***" or "===" or blank spaces.

If you already did use NetBSD pkgsrc, you can see that *every* MESSAGE
is composed like this :

===
$NetBSD: MESSAGE,v 1.1.1.1 2008/10/20 09:28:51 wiz Exp $

Note you need audio/audacious-plugins to actually play music.
===

I would do something like this to the FreeBSD ports, if you agree with
me I can check every messages and modify them. I can also put
something in the FreeBSD porter's handbook to write a "pkg-message
template"

I know that there is much more important work to do, that's why I can
take all this work for myself.

Please report any feedback,
With kind regards.

-- 
Demelier David
___
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 pkg-message[.in] guideline idea

[David DEMELIER]

2010/6/23 Wesley Shields :
> On Wed, Jun 23, 2010 at 02:16:07PM +0200, David DEMELIER wrote:
>> Hi freebsd-ports@,
>>
>> I would like to propose you something that I would like to be done.
>> It's a cosmetic, useless thing but I like when things are made
>> homogeneously. That is the problem : as you can see, sometimes port
>> tells a message to the user but some maintainers used delimiters to
>> begin/end the message such as a lot of "***" or "===" or blank spaces.
>>
>> If you already did use NetBSD pkgsrc, you can see that *every* MESSAGE
>> is composed like this :
>>
>> ===
>> $NetBSD: MESSAGE,v 1.1.1.1 2008/10/20 09:28:51 wiz Exp $
>>
>> Note you need audio/audacious-plugins to actually play music.
>> ===
>>
>> I would do something like this to the FreeBSD ports, if you agree with
>> me I can check every messages and modify them. I can also put
>> something in the FreeBSD porter's handbook to write a "pkg-message
>> template"
>>
>> I know that there is much more important work to do, that's why I can
>> take all this work for myself.
>
> I think a better solution is to do what portmaster does and display all
> the pkg-message files as one of the last things it does. I had a patch
> to do this sitting in portmgr@ queue but it needs more work.
>
> A combination of some standardization of pkg-message files and
> displaying them all at the end of a build would be best.
>
> -- WXS
>

Yes, Gentoo's portage emerge does this, if I remember well it prints
the message after building the port and when every port has finished
and that is really interesting !

Because I always used mv, vim, diff to generate patches I need some
time to learn the way to do patches with cvs.

-- 
Demelier David
___
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 pkg-message[.in] guideline idea

[David DEMELIER]

2010/6/23 Janne Snabb :
> On Wed, 23 Jun 2010, David DEMELIER wrote:
>
>> I would do something like this to the FreeBSD ports, if you agree with
>> me I can check every messages and modify them. I can also put
>> something in the FreeBSD porter's handbook to write a "pkg-message
>> template"
>
> I find it completely useless and plainly stupid to edit the
> pkg-messages of all ports to include lots of equal signs for tty-based
> formatting purposes. In my opinion the messages in the ports tree
> should contain (English language, word based) messages, and if some
> visual formatting is desired, it should be done by the upper layer
> which displays the message (such as the ports framework, a web site
> which displays information about various ports, or whatever).
>

We can take a long time to do that (we don't have to do it quickly),
but it could be useful to standardize it for one reason :
You will see that it's a message from the port maintainer/submitter
and not from the program itself! Sometimes configure scripts stage say
some useless things to the user.

> The more clueful web monkeys have known to separate content from
> visual formatting for several years, why should FreeBSD make the
> same mistake the web monkeys did when www first became popular?
>
> However I fully support the idea that all the relevant messages
> should be displayed at the end of a build/upgrade process whenever
> technically feasible (otherwise they will just fly past while I am
> having a lunch or whatever). If the boild/upgrade process fails in
> the middle, the messages of successful builds/upgrades should still
> be displayed, even though the end of the process has not been
> reached.
>

I agree too.

-- 
Demelier David
___
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 pkg-message[.in] guideline idea

[David DEMELIER]

2010/6/24 Janne Snabb :
> On Wed, 23 Jun 2010, David DEMELIER wrote:
>
>> 2010/6/23 Janne Snabb :
>>>
>>> I find it completely useless and plainly stupid to edit the
>>> pkg-messages of all ports to include lots of equal signs for tty-based
>>> formatting purposes.
>>
>> We can take a long time to do that (we don't have to do it quickly),
>> but it could be useful to standardize it for one reason :
>> You will see that it's a message from the port maintainer/submitter
>> and not from the program itself! Sometimes configure scripts stage say
>> some useless things to the user.
>
> You obviously did not get my point.
>
> I fully agree with you that displaying a line of equals signs on
> tty based interfaces to make the messages stand out from other crap
> when installing ports makes sense, but I STRONGLY oppose to the
> idea of putting this visual formatting in the actual message files.
> It is just not the right place to put it in.
>

I see, so maybe in the future you would like some tools that can print
the message, like a GTK+ dialog, QT dialog, or an other tool, if it's
your point I agree. I don't specially want a equal "==" line, I would
just something consistent, why not : nothing ? Yes we can just print
the text without any visual characters, and the [future] tool will
print the message as it want.

> As I pointed out in my previous message, these messages are displayed
> by various different means for different purposes by different
> pieces of software (on tty, through GUI, on web sites, etc). Some
> of that software does not exist right now, but may be implemented
> in future (I am thinking here of for example a Synaptic like tool
> for managing the installed software).
>
> A line of equals signs looks good on a 80 character wide tty screen
> when the important message is surrounded by other non-important
> output, but it just looks stupid when displayed by a GUI or on a
> web site. Putting the visual cues in pkg-messages files would require
> every other display mechanism to have a logic to strip them out
> (for example when displaying the message on X display as a word-wrapped
> pop-up-window of random width).
>
> Why not just change the current display logic to emit these visual
> cues on a tty when installing ports? It is a single edit to a single
> file and does not introduce useless clutter in approximately 2209
> pkg-message* files in the ports tree.
>
> I do realize that many of the current pkg-messages do include similar
> visual visual formatting already in a non-standard way. One port
> uses equals signs, another port uses hyphens, etc. Those should be
> all removed from pkg-messages when the ports infrastructure displays
> a standardized visual separator automatically.
>
> I do not oppose to the other related ideas (such as making a logic
> to optionally display a part of a message only when some option was
> enabled).
>
> --
> Janne Snabb / EPIPE Communications
> sn...@epipe.com - http://epipe.com/
>



-- 
Demelier David
___
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 pkg-message[.in] guideline idea

[David DEMELIER]

2010/6/24 Freddie Cash :
> On Thu, Jun 24, 2010 at 12:04 AM, David DEMELIER
>  wrote:
>> 2010/6/24 Janne Snabb :
>>> On Wed, 23 Jun 2010, David DEMELIER wrote:
>>>
>>>> 2010/6/23 Janne Snabb :
>>>>>
>>>>> I find it completely useless and plainly stupid to edit the
>>>>> pkg-messages of all ports to include lots of equal signs for tty-based
>>>>> formatting purposes.
>>>>
>>>> We can take a long time to do that (we don't have to do it quickly),
>>>> but it could be useful to standardize it for one reason :
>>>> You will see that it's a message from the port maintainer/submitter
>>>> and not from the program itself! Sometimes configure scripts stage say
>>>> some useless things to the user.
>>>
>>> You obviously did not get my point.
>>>
>>> I fully agree with you that displaying a line of equals signs on
>>> tty based interfaces to make the messages stand out from other crap
>>> when installing ports makes sense, but I STRONGLY oppose to the
>>> idea of putting this visual formatting in the actual message files.
>>> It is just not the right place to put it in.
>>>
>> I see, so maybe in the future you would like some tools that can print
>> the message, like a GTK+ dialog, QT dialog, or an other tool, if it's
>> your point I agree. I don't specially want a equal "==" line, I would
>> just something consistent, why not : nothing ? Yes we can just print
>> the text without any visual characters, and the [future] tool will
>> print the message as it want.
>
> No, what he's saying is:
>  - put the logic to print the separators into the appropriate bsd.*.mk file
>  - remove all separators from all pkg-message* files
>
> That way, you can update the separators at any time by editing a
> single file, instead of editing 20,000+ pkg-message files.  And, that
> way, future tools can override the separator set in the mk file.
>
> Leave the pkg-message files as unformatted text.  Put the formatting
> into the mk file.
>
> Separate content from style.
>

Yes, that was I said, sorry if you did not understand well :-)

-- 
Demelier David
___
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: pidgin crashes everytime

[David DEMELIER]

It stops with :

(13:32:19) msn: msn_slplink_process_msg: slpmsg complete
(13:32:19) msn: C: SB 003: OUT
(13:32:19) msn: destroy httpconn (0x809609e40)
(13:32:19) stun: using server
zsh: bus error (core dumped)  pidgin -d

Maybe a msn failure.

-- 
Demelier David
___
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"

Conky fails to build with audacious option.

[David DEMELIER]

Hi

This is what happened when you try to compile sysutils/conky with the
audacious option :

===>  Building for conky-1.7.2_7
Making all in src
gmake[1]: Entering directory
`/usr/obj/usr/ports/sysutils/conky/work/conky-1.7.2/src'
gmake  all-am
gmake[2]: Entering directory
`/usr/obj/usr/ports/sysutils/conky/work/conky-1.7.2/src'
/bin/sh ../libtool --tag=CC   --mode=link cc -D_REENTRANT
-D_THREAD_SAFE -I/usr/local/include -I/usr/local/include/glib-2.0
-I/usr/local/lib/glib-2.0/include -I/usr/local/include/gtk-2.0
-I/usr/local/include/pango-1.0 -I/usr/local/include/cairo
-I/usr/local/include/libmowgli -I/usr/local/include/dbus-1.0
-I/usr/local/include/dbus-1.0/include -I/usr/local/lib/gtk-2.0/include
-I/usr/local/include/atk-1.0 -I/usr/local/include/gio-unix-2.0/
-I/usr/local/include/pixman-1 -I/usr/local/include/freetype2
-D_THREAD_SAFE -I/usr/local/include   -I/usr/local/include
-I/usr/local/include/freetype2   -D_THREAD_SAFE -I/usr/local/include
-D_THREAD_SAFE -I/usr/local/include   -D_THREAD_SAFE
-I/usr/local/include -I/usr/local/include/freetype2   -Wall -W -O2
-pipe -fno-strict-aliasing -pthread -lm -L/usr/local/lib -o conky
conky-conf_cookie.o conky-audacious.o  conky-colours.o conky-common.o
conky-conky.o conky-freebsd.o conky-diskio.o conky-fs.o
conky-mail.o conky-mixer.o conky-mpd.o conky-libmpdclient.o
conky-moc.o   conky-timed_thread.o conky-mboxscan.o conky-x11.o
conky-fonts.o   conky-specials.o conky-tailhead.o conky-temphelper.o
conky-text_object.o conky-algebra.o conky-imlib2.o   -pthread
-L/usr/local/lib -laudcore -lgtk-x11-2.0 -lmcs -lgdk-x11-2.0 -latk-1.0
-lgdk_pixbuf-2.0 -lpangocairo-1.0 -lXext -lXrender -lXinerama -lXi
-lXrandr -lXcursor -lXcomposite -lXdamage -lpangoft2-1.0 -lgio-2.0
-lXfixes -lcairo -lX11 -lpango-1.0 -lm -lfreetype -lfontconfig
-lgmodule-2.0 -lmowgli -ldbus-glib-1 -ldbus-1 -lgobject-2.0
-lgthread-2.0 -lglib-2.0   -lm -L/usr/local/lib -lX11
-L/usr/local/lib -lImlib2   -liconv -L/usr/local/lib -lXext
-L/usr/local/lib -lXdamage -lXfixes   -L/usr/local/lib -lXft -lXrender
-lfontconfig -lfreetype -lX11   -lkvm -ldevstat
libtool: link: cc -D_REENTRANT -D_THREAD_SAFE -I/usr/local/include
-I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include
-I/usr/local/include/gtk-2.0 -I/usr/local/include/pango-1.0
-I/usr/local/include/cairo -I/usr/local/include/libmowgli
-I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include
-I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0
-I/usr/local/include/gio-unix-2.0/ -I/usr/local/include/pixman-1
-I/usr/local/include/freetype2 -D_THREAD_SAFE -I/usr/local/include
-I/usr/local/include -I/usr/local/include/freetype2 -D_THREAD_SAFE
-I/usr/local/include -D_THREAD_SAFE -I/usr/local/include
-D_THREAD_SAFE -I/usr/local/include -I/usr/local/include/freetype2
-Wall -W -O2 -pipe -fno-strict-aliasing -pthread -o conky
conky-conf_cookie.o conky-audacious.o conky-colours.o conky-common.o
conky-conky.o conky-freebsd.o conky-diskio.o conky-fs.o conky-mail.o
conky-mixer.o conky-mpd.o conky-libmpdclient.o conky-moc.o
conky-timed_thread.o conky-mboxscan.o conky-x11.o conky-fonts.o
conky-specials.o conky-tailhead.o conky-temphelper.o
conky-text_object.o conky-algebra.o conky-imlib2.o -pthread
-L/usr/local/lib -laudcore /usr/local/lib/libgtk-x11-2.0.so -lmcs
/usr/local/lib/libgdk-x11-2.0.so /usr/local/lib/libatk-1.0.so
/usr/local/lib/libgdk_pixbuf-2.0.so
/usr/local/lib/libpangocairo-1.0.so /usr/local/lib/libXinerama.so
/usr/local/lib/libXi.so /usr/local/lib/libXrandr.so
/usr/local/lib/libXcursor.so /usr/local/lib/libXcomposite.so
/usr/local/lib/libpangoft2-1.0.so /usr/local/lib/libgio-2.0.so
/usr/local/lib/libcairo.so /usr/local/lib/libpixman-1.so
/usr/local/lib/libglitz.so -lpng /usr/local/lib/libxcb-render-util.so
/usr/local/lib/libxcb-render.so /usr/local/lib/libpango-1.0.so
/usr/local/lib/libgmodule-2.0.so -lmowgli
/usr/local/lib/libdbus-glib-1.so /usr/local/lib/libdbus-1.so
/usr/local/lib/libgobject-2.0.so /usr/local/lib/libgthread-2.0.so
/usr/local/lib/libglib-2.0.so /usr/local/lib/libintl.so
/usr/local/lib/libpcre.so /usr/local/lib/libImlib2.so -lm
/usr/local/lib/libiconv.so /usr/local/lib/libXext.so
/usr/local/lib/libXdamage.so /usr/local/lib/libXfixes.so
/usr/local/lib/libXft.so /usr/local/lib/libXrender.so
/usr/local/lib/libfontconfig.so /usr/local/lib/libexpat.so
/usr/local/lib/libfreetype.so -lz /usr/local/lib/libX11.so
/usr/local/lib/libxcb.so /usr/local/lib/libXau.so
/usr/local/lib/libXdmcp.so /usr/local/lib/libpthread-stubs.so -lrpcsvc
-lkvm -ldevstat -pthread -Wl,-rpath -Wl,/usr/local/lib -Wl,-rpath
-Wl,/usr/local/lib
conky-audacious.o(.text+0x162): In function `audacious_thread_func':
: undefined reference to `audacious_remote_is_running'
conky-audacious.o(.text+0x16e): In function `audacious_thread_func':
: undefined reference to `audacious_remote_is_paused'
conky-audacious.o(.text+0x198): In function `audacious_thread_func':
: undefined reference to `audacious_remote_get_playlist_pos'
conky-audacious.o(.text+0x1a

Re: dspam install

[David DEMELIER]

2010/7/11 Sahil Tandon :
> On Sun, 2010-07-11 at 13:51:51 -0700, Jim Pazarena wrote:
>
>> tried to make mail/dspam and it exits nagging that it
>> requires MySQL 5.0 client, where I have MySQL 5.1
>>
>> Is there a way to convince the dspam routine that
>> 5.1 is acceptable? (presuming that it IS).
>
> Yes, 'make config' and choose MYSQL51 (MYSQL50 is the default).  Or:
>
> % make WITH_MYSQL51=1 WITHOUT_MYSQL50=1
>
> --
> Sahil Tandon 
> ___
> 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 think this :

.ifdef(WITH_MYSQL40)
WANT_MYSQL_VER= 40
#PKGNAMESUFFIX= -mysql40
.elifdef(WITH_MYSQL41)
WANT_MYSQL_VER= 41
#PKGNAMESUFFIX= -mysql41
.elifndef(WITHOUT_MYSQL50)
WANT_MYSQL_VER= 50
#PKGNAMESUFFIX= -mysql50
.elifdef(WITH_MYSQL51)
WANT_MYSQL_VER= 51
#PKGNAMESUFFIX= -mysql51
.elifdef(WITH_MYSQL55)
WANT_MYSQL_VER= 55
#PKGNAMESUFFIX= -mysql55
.endif

could be replaced by :

.if defined(WITH_MYSQL)
WANT_MYSQL_VER= 55 ...
.endif

Then if the user wants a different version he still can change using :
WITH_MYSQL_VER= 44.

Why don't keep it simple and simple? And why don't use things how they
should be used? I think there is still a lot of problems in many
ports. We must make a big KISS cleanup in the ports tree to make it as
good as NetBSD' pkgsrc.

Kind regards.

-- 
Demelier David
___
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: vlc install error - possibly plist error for kde4?

[David DEMELIER]

2010/7/12 David Southwell :
> Hi
> The following error occurs on portupgrade of vlc
>
> #uname -a
> FreeBSD dns1.vizion2000.net 7.2-RELEASE-p3 FreeBSD 7.2-RELEASE-p3 #0: Thu Aug
> 20 12:54:34 BST 2009
>
> da...@dns1.vizion2000.net:/usr/obj/usr/src/sys/GENERIC  amd64
> cd /usr/ports/multimedia/vlc/work/fake/usr/local/share/icons && /usr/bin/find
> -s * -type f -o -type l |  /usr/bin/sed -e 's|^|share/icons/|' >>
> /usr/ports/multimedia/vlc/work/plist  && /usr/bin/find -d * -type d |
> /usr/bin/sed -e 's|^|@dirrmtry share/icons/|' >>
> /usr/ports/multimedia/vlc/work/plist
> echo "@dirrmtry share/icons" >> /usr/ports/multimedia/vlc/work/plist
> cd /usr/ports/multimedia/vlc/work/fake/usr/local/share/kde4 && /usr/bin/find -
> s * -type f -o -type l |  /usr/bin/sed -e 's|^|share/kde4/|' >>
> /usr/ports/multimedia/vlc/work/plist  && /usr/bin/find -d * -type d |
> /usr/bin/sed -e 's|^|@dirrmtry share/kde4/|' >>
> /usr/ports/multimedia/vlc/work/plist
> cd: can't cd to /usr/ports/multimedia/vlc/work/fake/usr/local/share/kde4
> *** Error code 2
>
> Stop in /usr/ports/multimedia/vlc.
> *** Error code 1
>
> Stop in /usr/ports/multimedia/vlc.
> *** Error code 1
>
> Stop in /usr/ports/multimedia/vlc.
> ** Command failed [exit code 1]: /usr/bin/script -qa
> /tmp/portupgrade20100712-32475-1ouopy-0 env UPGRADE_TOOL=portupgrade
> UPGRADE_PORT=vlc-1.0.6_3,3 UPGRADE_PORT_VER=1.0.6_3,3 make reinstall
> --->  Restoring the old version
> ** Fix the installation problem and try again.
> [Updating the pkgdb  in /var/db/pkg ... - 1311 packages
> found (-0 +1) . done]
> ** Listing the failed packages (-:ignored / *:skipped / !:failed)
>        ! multimedia/vlc (vlc-1.0.6_3,3)        (install error)
> You have new mail.
> dns1#
>
>
> Photographic Artist
> Permanent Installations & Design
> Creative Imagery and Advanced Digital Techniques
> High Dynamic Range Photography & Official Portraiture
> Combined darkroom & digital creations
> & Systems Adminstrator for the vizion2000.net network
> ___
> 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 don't understand this : cd: can't cd to
/usr/ports/multimedia/vlc/work/fake/usr/local/share/kde4

do you use a fakeroot ?

-- 
Demelier David
___
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: dspam install

[David DEMELIER]

2010/7/13 Sahil Tandon :
> On Mon, 2010-07-12 at 21:28:56 +0200, David DEMELIER wrote:
>
>> .if defined(WITH_MYSQL)
>> WANT_MYSQL_VER= 55 ...
>> .endif
>>
>> Then if the user wants a different version he still can change using :
>> WITH_MYSQL_VER= 44.
>
> That change by itself will not work because in bsd.database.mk:
>
>  .if defined(WITH_MYSQL_VER) && ${WITH_MYSQL_VER} != ${WANT_MYSQL_VER}
>  IGNORE= ...
>

Then, explain me why do both php5 and php5-pgsql have not
KNOBS/OPTIONS like dspam and work with this variable WITH_PGSQL_VER ?

$ pwd
/usr/ports/databases/php5-pgsql
$ WITH_PGSQL_VER=83 make all-depends-list
/usr/ports/lang/php5
[...]
/usr/ports/databases/postgresql83-client
[...]
$ WITH_PGSQL_VER=84 make all-depends-list
/usr/ports/lang/php5
[...]
/usr/ports/databases/postgresql84-client
[...]

>> Why don't keep it simple and simple?
>
> I am not sure what you mean.  Complexity is not a goal of the project.
> If you have an idea that does not forfeit existing functionality or
> violate POLA, please submit it as a patch.
>
>> And why don't use things how they should be used?
>
> Once again, I am confused by your question.  Please clarify your
> meaning.
>

Because I meant, if someone made these KNOBS, that's would suppose
they should be used. As shown just above it works with php5-pgsql.

So if a variable could be used to specify a specific version, it must
be used instead of a couple of option that set the package version. I
think WITH_MYSQL_VER and WITH_PGSQL_VER were made for that. (There is
one for apache too)

>> I think there is still a lot of problems in many ports.
>
> I think we all agree that there is room for improvement.  Since you have
> identified many problems, I look forward to your PRs.
>
>> We must make a big KISS cleanup in the ports tree to make it as good
>> as NetBSD' pkgsrc.
>
> Please send PRs or provide specific details; general comments like the
> above are not helpful.

Yes sometime I'm nasty with people, I'm sorry about that but when I
saw this port I just didn't understand.

I apologize for my english.

-- 
Demelier David
___
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: dspam install

[David DEMELIER]

2010/7/14 Jim Pazarena :
> Sahil Tandon wrote:
>>
>> [mail/dspam maintainer Cc:'d]
>>
>> On Tue, 2010-07-13 at 09:46:04 +0200, David DEMELIER wrote:
>>
>>> 2010/7/13 Sahil Tandon :
>>>>
>>>> On Mon, 2010-07-12 at 21:28:56 +0200, David DEMELIER wrote:
>>>
>>> Yes sometime I'm nasty with people, I'm sorry about that but when I
>>> saw this port I just didn't understand.
>>
>> What did you not understand?
>>
>>> I apologize for my english.
>>
>> No apology needed, as that is not the problem here.
>
> my own ports confusion (in general) is that in some ports
> you use a "-Dxx" to define a required (or not required) option
> while in others (at least dspam) you use WITHOUT_xxx or WITH_xxx=1.
> It would be nice if all ports has the same standard of definitions.
>
> Or... am I confused?

If FreeBSD people agree, KNOBS will be removed in the future (but this
will take a long long time).

-- 
Demelier David
___
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: dspam install

[David DEMELIER]

2010/7/14 Sahil Tandon :
> [mail/dspam maintainer Cc:'d]
>
> On Tue, 2010-07-13 at 09:46:04 +0200, David DEMELIER wrote:
>
>> 2010/7/13 Sahil Tandon :
>> > On Mon, 2010-07-12 at 21:28:56 +0200, David DEMELIER wrote:
>> >
>> >> .if defined(WITH_MYSQL)
>> >> WANT_MYSQL_VER= 55 ...
>> >> .endif
>> >>
>> >> Then if the user wants a different version he still can change using :
>> >> WITH_MYSQL_VER= 44.
>> >
>> > That change by itself will not work because in bsd.database.mk:
>> >
>> >  .if defined(WITH_MYSQL_VER) && ${WITH_MYSQL_VER} != ${WANT_MYSQL_VER}
>> >  IGNORE= ...
>>
>> Then, explain me why do both php5 and php5-pgsql have not
>> KNOBS/OPTIONS like dspam and work with this variable WITH_PGSQL_VER ?
>
> This is a good opportunity for you to learn about how the ports system
> works.  Compare the contents of both ports and also review
> bsd.database.mk; if, after that, you still do not understand the current
> behavior, let us know.
>

I'm writing a brand new mail/dspam port from scratch, if I finally
finish it in the next fews days I will show you. The only problem I
have for now is that there is no WITH_CYRUS_VER like variable so I
can't make a per-user defined variable for which cyrus version to
install.

>> Because I meant, if someone made these KNOBS, that's would suppose
>> they should be used. As shown just above it works with php5-pgsql.
>>
>> So if a variable could be used to specify a specific version, it must
>> be used instead of a couple of option that set the package version. I
>> think WITH_MYSQL_VER and WITH_PGSQL_VER were made for that. (There is
>> one for apache too)
>
> I appreciate your frustration, but please realize that there are often
> many ways to accomplish the same task.  Trade-offs are involved. If you
> believe a port can be improved, please (and now I'm repeating myself)
> submit a patch!  If you are unable to create a patch, then clearly
> explain your idea in pseudo-code and submit it as a PR for the
> maintainer's consideration.  If you have trouble creating a patch, also
> feel free to ping me off-list; I'm happy to work with you on this.
>
>> >> We must make a big KISS cleanup in the ports tree to make it as good
>> >> as NetBSD' pkgsrc.
>> >
>> > Please send PRs or provide specific details; general comments like the
>> > above are not helpful.
>>
>> Yes sometime I'm nasty with people, I'm sorry about that but when I
>> saw this port I just didn't understand.
>
> What did you not understand?
>
>> I apologize for my english.
>
> No apology needed, as that is not the problem here.
>
> --
> Sahil Tandon 
> ___
> 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"
>



-- 
Demelier David
___
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"

net-im/libpurple forgot to remove patches?

[David DEMELIER]

Hi,

I saw the update of pidgin so I wanted to upgrade but it fails :

===>>> Port directory: /usr/ports/net-im/libpurple
===>>> Starting check for build dependencies
===>>> Gathering dependency list for net-im/libpurple from ports
===>>> Starting dependency check
===>>> Dependency check complete for net-im/libpurple
===>  Cleaning for libpurple-2.7.2

===>  Vulnerability check disabled, database not found
===>  License check disabled, port has not defined LICENSE
===>  Found saved configuration for libpurple-2.7.1
===>  Extracting for libpurple-2.7.2
=> MD5 Checksum OK for pidgin-2.7.2.tar.bz2.
=> SHA256 Checksum OK for pidgin-2.7.2.tar.bz2.
===>  Patching for libpurple-2.7.2
===>  Applying FreeBSD patches for libpurple-2.7.2
Ignoring previously applied (or reversed) patch.
1 out of 1 hunks ignored--saving rejects to
libpurple/protocols/oscar/oscar.c.rej
=> Patch patch-libpurple_protocols_oscar_oscar.c failed to apply cleanly.
=> Patch(es) patch-finch_libgnt_gntwm.c
patch-libpurple-media-backend-fs2.h
patch-libpurple-protocols-zephyr-Zinternal.c applied cleanly.
*** Error code 1

Stop in /usr/ports/net-im/libpurple.
*** Error code 1

Stop in /usr/ports/net-im/libpurple.

===>>> make failed for net-im/libpurple
===>>> Aborting update

===>>> Update for libpurple-2.7.1 failed
===>>> Aborting update

Maybe the committer forgot to remove these patches ?

-- 
Demelier David
___
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/ languages categories

[David DEMELIER]

Hello,

I personally think that categories like french, japanese, arabic,
etc... are not the best way to write a language dependant port. Now,
there is no many languages categories in the ports tree but we can
plan that in the future more directories for the new future languages
dependant port can be added. Example : if someone write a new aspell
language that is not in the ports tree, we must create a new directory
in the ports tree ports/.

For example: there is no ports/italian directory now, will you create
a new italian directory if we must add aspell for italian? (no it's in
textproc/it-aspell and it's confusing)

I think we must remove all these languages directories and just keep
it simple and simple like all the textproc/*-aspell.

The best way to separate ports to language dependant port is just
prefixing the port with the good language such as :

fr-kde4-l10n
fr-aspell
de-ispell

and so on. It's so easier to maintain and so much cleaner !

I hope you will agree with me.

With kind regards.

-- 
Demelier David
___
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: net-im/libpurple forgot to remove patches?

[David DEMELIER]

2010/7/25 Sahil Tandon :
> On Sun, 2010-07-25 at 10:29:19 -0400, Sahil Tandon wrote:
>
>> On Sun, 2010-07-25 at 12:01:06 +0200, David DEMELIER wrote:
>>
>> > ===>  Patching for libpurple-2.7.2
>> > ===>  Applying FreeBSD patches for libpurple-2.7.2
>> > Ignoring previously applied (or reversed) patch.
>> > 1 out of 1 hunks ignored--saving rejects to
>> > libpurple/protocols/oscar/oscar.c.rej
>> > => Patch patch-libpurple_protocols_oscar_oscar.c failed to apply cleanly.
>> >
>> > Maybe the committer forgot to remove these patches ?
>>
>> Thanks for your report. The committer has already been alerted:
>>
>>  http://lists.freebsd.org/pipermail/cvs-ports/2010-July/199204.html
>>
>> So the problem will be fixed when he has time.
>
> Fixed:
>
>  http://lists.freebsd.org/pipermail/cvs-ports/2010-July/199221.html
>
> --
> Sahil Tandon 
> ___
> 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"
>

Perfect, thanks :-)

-- 
Demelier David
___
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"

games/connect4 segfaults.

[David DEMELIER]

Hi,

I just wanted to try games/connect4 but it segfaults here on FreeBSD
8.1-RELEASE and amd64.

It's a long backtrace so I think you should try it by yourself.

Kind regards.

-- 
Demelier David
___
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 pkg-message[.in] guideline idea

[David DEMELIER]

2010/6/24 Garrett Cooper :
> On Thu, Jun 24, 2010 at 9:43 AM, David DEMELIER
>  wrote:
>> 2010/6/24 Freddie Cash :
>>> On Thu, Jun 24, 2010 at 12:04 AM, David DEMELIER
>>>  wrote:
>>>> 2010/6/24 Janne Snabb :
>>>>> On Wed, 23 Jun 2010, David DEMELIER wrote:
>>>>>
>>>>>> 2010/6/23 Janne Snabb :
>>>>>>>
>>>>>>> I find it completely useless and plainly stupid to edit the
>>>>>>> pkg-messages of all ports to include lots of equal signs for tty-based
>>>>>>> formatting purposes.
>>>>>>
>>>>>> We can take a long time to do that (we don't have to do it quickly),
>>>>>> but it could be useful to standardize it for one reason :
>>>>>> You will see that it's a message from the port maintainer/submitter
>>>>>> and not from the program itself! Sometimes configure scripts stage say
>>>>>> some useless things to the user.
>>>>>
>>>>> You obviously did not get my point.
>>>>>
>>>>> I fully agree with you that displaying a line of equals signs on
>>>>> tty based interfaces to make the messages stand out from other crap
>>>>> when installing ports makes sense, but I STRONGLY oppose to the
>>>>> idea of putting this visual formatting in the actual message files.
>>>>> It is just not the right place to put it in.
>>>>>
>>>> I see, so maybe in the future you would like some tools that can print
>>>> the message, like a GTK+ dialog, QT dialog, or an other tool, if it's
>>>> your point I agree. I don't specially want a equal "==" line, I would
>>>> just something consistent, why not : nothing ? Yes we can just print
>>>> the text without any visual characters, and the [future] tool will
>>>> print the message as it want.
>>>
>>> No, what he's saying is:
>>>  - put the logic to print the separators into the appropriate bsd.*.mk file
>>>  - remove all separators from all pkg-message* files
>>>
>>> That way, you can update the separators at any time by editing a
>>> single file, instead of editing 20,000+ pkg-message files.  And, that
>>> way, future tools can override the separator set in the mk file.
>>>
>>> Leave the pkg-message files as unformatted text.  Put the formatting
>>> into the mk file.
>>>
>>> Separate content from style.
>>>
>>
>> Yes, that was I said, sorry if you did not understand well :-)
>
> The only problem is that pushing all of this logic into bsd.*.mk only
> solves half the problem: from source installations. It doesn't cover
> binary installations via pkg_install.
>
> I think Doug and Phillip were on the right track with pushing the data
> into a pkg_install consumable format, but the only problem is that
> creating additional code that handles one more corner case for
> @comment will serve to only slow down the plist parser unnecessarily.
> That's why I was suggesting a scripting infrastructure, like so:
>
> pkgmsg() {
>    local message=$1
>    pkgmsg_separator
>    echo "$message"
>    pkgmsg_separator
> }
>
> Example:
>
> echo "This is an install message for my awesome new package
> foo-" > +DISPLAY
> pkgmsg `cat +DISPLAY`
>
> And considering that you almost get the functionality for free via
> pkg_install (from pkg_create(8)):
>
>     -D displayfile
>             Display the file (by concatenating it to stdout) after installing
>             the package.  Useful for things like legal notices on almost-free
>             software, etc.
>
> The thing about using a script function like pkgmsg too is that it can
> be dynamically overwritten by certain groups in order to tailor the
> messages (or mute output for customer purposes after everything has
> passed QA if they use pkg_install in a product) to the meet their
> needs when doing localized installations or deployments as well.
>
> So, why not just add the relevant bits as I described?
>
> Thanks,
> -Garrett
>

I like this idea,

in fact the best thing to do would be to remove any kind of decoration
and just keeping the text in the pkg-message. Then we could write
something like the SECURITY REPORT.

So it would be something like that :

===> SECURITY REPORT:
  This port has installed the following files which may act as network
  servers and may therefore pose a remote security risk to the system.
/usr/local/lib/libtorrent-raste

Re: dspam install

[David DEMELIER]

2010/7/16 Ion-Mihai Tetcu :
> On Thu, 15 Jul 2010 22:50:32 +0200
> David DEMELIER  wrote:
>
>> 2010/7/14 Sahil Tandon :
>> > [mail/dspam maintainer Cc:'d]
>> >
>> > On Tue, 2010-07-13 at 09:46:04 +0200, David DEMELIER wrote:
>> >
>> >> 2010/7/13 Sahil Tandon :
>> >> > On Mon, 2010-07-12 at 21:28:56 +0200, David DEMELIER wrote:
>> >> >
>> >> >> .if defined(WITH_MYSQL)
>> >> >> WANT_MYSQL_VER= 55 ...
>> >> >> .endif
>> >> >>
>> >> >> Then if the user wants a different version he still can change using :
>> >> >> WITH_MYSQL_VER= 44.
>> >> >
>> >> > That change by itself will not work because in bsd.database.mk:
>> >> >
>> >> >  .if defined(WITH_MYSQL_VER) && ${WITH_MYSQL_VER} != ${WANT_MYSQL_VER}
>> >> >  IGNORE= ...
>> >>
>> >> Then, explain me why do both php5 and php5-pgsql have not
>> >> KNOBS/OPTIONS like dspam and work with this variable WITH_PGSQL_VER ?
>> >
>> > This is a good opportunity for you to learn about how the ports system
>> > works.  Compare the contents of both ports and also review
>> > bsd.database.mk; if, after that, you still do not understand the current
>> > behavior, let us know.
>
> For short, it's like this because it (AFAIR) not all what we have now
> in the framework we had back when I worte the port, and because I
> wanted to also be able to depend on the server.
>
>
> --
> Ion-Mihai Tetcu 
>

Hi,

I made a lot of changes in the mail/dspam Makefile.

Can you take a look at it if you have the time? I want to be sure
everything is okay and I didn't test everything right now.

The patch is accessible here :

http://markand.malikania.fr/dspam.patch

Summary of changes :
 o Huge general cleanup ;
 o Removed useless *_LOCAL options (for RUN_DEPENDS). If user needs it
he will install it ;
 o Sit on WITH_MYSQL_VER and WITH_PGSQL_VER instead of multiple
WITH_MYSQL* options ;
 o Renamed WebUI option to WEBUI (we usually write them in capital only) ;
 o Switched USE_* conditionals to WITH_* (depend on option selected).

With kind regards.

-- 
Demelier David
___
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: Proposal for new UPDATING format

[David DEMELIER]

2010/8/19 Andres Perera :
> The idea is to add a VERSION field so that automated tools can display
> the entries prior performing the actual upgrade.
>
> Filtering by date isn't exact enough, so the new field will correspond
> with the first version of the port were the "problem" occurs.
>
> Without getting into implementation details, the port management tools
> could use a line similar to::
>
> % pkg_updating clang-1.2
>
> Matching the version with whatever it's installing...
>

Not a bad idea, the problem is that the file UPDATING does not speak
always for a package, sometime it's just some information that are not
specific to a package.

-- 
Demelier David
___
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: drop maintainership from games/wesnoth{,-devel} to ports@

[David DEMELIER]

2010/8/23 Philip Paeps :
> On 2010-08-23 08:56:18 (+0400), Anonymous  wrote:
>> I kinda hate having to wait for a timeout instead of approval. If not
>> timeouts then you're just too slow, committing an update just before
>> next release. This makes window for players to report bugs about -devel
>> release to upstream too narrow if not nonexistent.
>>
>> In hopes ports/149899 will be comitted before 1.9.1 is released.
>
> Actually - I would be happy to change the maintainer field to either of you,
> so you can file bugs as "maintainer updates".  Would that be alright?  Who
> wants to be maintainer? :-)
>

I would like :-). Please add markand (at) malikania (dot) fr then if you agree.

>  - Philip
>
> --
> Philip Paeps                                       Always read the label
> phi...@freebsd.org
>
>  "Do not meddle in the affairs of wizards because a refusal often offends,
>  I read somewhere."
>          -- (Terry Pratchett, Mort)
> ___
> 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"
>



-- 
Demelier David
___
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"

Legal music and sound issues with games/viruskiller

[David Demelier]

Hi,

We rewrote the games/viruskiller with one option, MUSIC. The musics and 
sounds have legal issues and that is specified here :


http://www.happypenguin.org/forums/viewtopic.php?t=4725

Because I wanted to write this port, I made this option to interact with 
the user. He needs to enable the option to use the sounds and musics.


I also said in the comment options that the files are non-free, then the 
user is completely warned.


Do you agree with this Makefile now ?

--- Makefile.orig   2010-08-25 19:20:40.0 +0200
+++ Makefile2010-08-25 20:06:48.0 +0200
@@ -20,15 +20,26 @@
 USE_SDL=   mixer image ttf net
 USE_GMAKE= yes

+NO_CDROM=  yes
+
 INSTALLS_ICONS=yes

 WRKSRC=${WRKDIR}/${PORTNAME}-${PORTVERSION}

 MAKEFILE=  makefile

+OPTIONS=   MUSIC "Enable musics (non-free)" Off
+
+.include 
+
+.if !defined(WITH_MUSIC)
+SUB_FILES= pkg-message
+.endif
+
 post-patch:
-   # Remove non-free restricted files:
-   ${RM} -f ${WRKSRC}/music/* ${WRKSRC}/sound/*
+.if !defined(WITH_MUSIC)
+   @${REINPLACE_CMD} -e "s|music||g;s|sound||g" ${WRKSRC}/makefile
+.endif

 .if defined(NOPORTDOCS)
@${REINPLACE_CMD} -e "s|^.*install.*DOCS.*||g" \
@@ -40,4 +51,9 @@
-e "s|^DATADIR.*|DATADIR=${DATADIR}/|g" \
-e "s|^DOCDIR.*|DOCDIR=${DOCSDIR}|g" ${WRKSRC}/makefile

+post-install:
+.if !defined(WITH_MUSIC)
+   @${CAT} ${PKGMESSAGE}
+.endif
+
 .include 
--- /dev/null   2010-08-25 20:08:43.0 +0200
+++ files/pkg-message.in2010-08-25 20:05:20.0 +0200
@@ -0,0 +1,2 @@
+Because you disabled music you need to start viruskiller with the 
-noaudio flag,

+otherwise it will segfaults.

I think with this, we could keep the game in the ports/ tree.

With kind regards.
___
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"

Problem with www/p5-Jifty

[David DEMELIER]

Hello folks,

I have some troubles running jifty help after installed it :

mark...@melon ~/devel/Hello $ jifty help
Devel::StackTrace does not define $Devel::StackTrace::VERSION--version
check failed at
/usr/local/lib/perl5/site_perl/5.10.1/Exception/Class/Base.pm line 10.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.10.1/Exception/Class/Base.pm line 10.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.10.1/Exception/Class.pm line 10.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.10.1/Exception/Class.pm line 10.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.10.1/HTML/Mason/Exceptions.pm line
73.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.10.1/HTML/Mason/Exceptions.pm line
73.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.10.1/Jifty/View/Declare/Handler.pm
line 9.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.10.1/Jifty/View/Declare/Handler.pm
line 9.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.10.1/Jifty/Handler.pm line 29.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.10.1/Jifty/Handler.pm line 29.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.10.1/Jifty/Everything.pm line 56.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.10.1/Jifty/Everything.pm line 56.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.10.1/Jifty.pm line 103.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.10.1/Jifty.pm line 103.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.10.1/Jifty/Util.pm line 15.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.10.1/Jifty/Util.pm line 15.
Compilation failed in require at /usr/local/bin/jifty line 7.
BEGIN failed--compilation aborted at /usr/local/bin/jifty line 10.

I don't know if it's an upstream problem or a problem with
devel/p5-Devel-StackTrace. I asked to the jifty developers but for the
moment I don't have any answers from them.

Do you have any idea to fix this ?

Kind regards.

-- 
Demelier David
___
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: [ports/net/isc-dhcp*] Don't stop DHCP related daemons

[David DEMELIER]

2010/9/12 Ion-Mihai Tetcu :
> On Sun, 12 Sep 2010 06:45:47 +0800
> Denny Lin  wrote:
>
>> On Sat, Sep 11, 2010 at 11:35:43PM +0200, Torfinn Ingolfsen wrote:
>> > On Sat, Sep 11, 2010 at 4:33 PM, Ion-Mihai Tetcu
>> >  wrote:
>> >
>> > > This 'stop the service before we install' seems to be a new
>> > > fashion, usually unneeded/disruptive.
>> > > IMO this should only happen when it's really needed, and with
>> > > some big warning printed.
>> > >
>> >
>> > And perhaps with a restart service attempt afterwards? (maybe
>> > interactive as in "do you want me to restart the service y/n?")
>> > Just my 0.02 euros.
>>
>> How about knobs like WITH_STOP_SERVICE and WITH_START_SERVICE for
>> users who wish to avoid the y/n questions?
>
> We have a standard policy of not auto-starting anything.
> We really don't want a service to be stated automatically after install
> (think: I installed this today, I'll configure it how I need it
> tomorrow, then start the service).
> And you can't really know if it's a new install or an upgrade.
>
> --
> IOnut - Un^d^dregistered ;) FreeBSD "user"
>  "Intellectual Property" is   nowhere near as valuable   as "Intellect"
> FreeBSD committer -> ite...@freebsd.org, PGP Key ID 057E9F8B493A297B
>

The the policy should to the same for stopping services and do not
auto-stop them because we can't see if it's an upgrade neither.

-- 
Demelier David
___
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: [PATCH] enable MAKE_JOBS_SAFE for Vim build

[David DEMELIER]

2010/9/9 David O'Brien :
> This patch allows me to build Vim in parallel.
>
> Give it a try if you're interested.  Please let me know if you are
> UNABLE to build with this patch applied.
> [I only need to know of failures, thanks.]
>
> --
> -- David  (obr...@freebsd.org)
>
> Index: Makefile
> ===
> RCS file: /home/pcvs/ports/editors/vim/Makefile,v
> retrieving revision 1.356
> diff -u -p -r1.356 Makefile
> --- Makefile    9 Sep 2010 06:06:28 -       1.356
> +++ Makefile    9 Sep 2010 07:48:48 -
> @@ -39,7 +39,7 @@ SLAVEDIRS=    editors/vim-lite
>  .endif
>
>  CONFLICTS=     vim6* vim*-lite
> -MAKE_JOBS_UNSAFE= yes
> +MAKE_JOBS_SAFE=        yes
>  USE_BZIP2=     yes
>  DIST_SUBDIR=   vim
>  WRKSRC=                ${WRKDIR}/vim${PORTVERSION:C/\.[0-9]*$//:S/.//g}/src
> @@ -195,6 +195,9 @@ post-patch:
>                ${REINPLACE_CMD} -e 's,ctags -R \.,${CTAGS_CMD},g')
>
>  pre-configure:
> +       # Fix dependency misspelling so that 'make -j#' will work.
> +       @${REINPLACE_CMD} -e 's|\./auto/osdef\.h|auto/osdef.h|g' \
> +               ${WRKSRC}/Makefile
>        @(cd ${WRKSRC} ; ${MAKE} distclean)
>       �...@${reinplace_cmd} -e ' \
>                s|\$$gtk_config_prefix/bin/gtk-config|\$${GTK_CONFIG}|g; \
> @@ -207,6 +210,9 @@ pre-configure:
>                ${WRKSRC}/feature.h
>  .endif
>
> +post-configure:
> +       @(cd ${WRKSRC} ; ${MAKE} scratch config)
> +
>  #      Clean up junk files to keep them from being installed.
>  pre-install:
>       �...@${find} ${WRKSRC:H} -type f -name '*.orig' -delete
> ___
> 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"
>

Here it works, just missing real OPTIONS framework and this port will
be perfect :-).

Kind regards,

-- 
Demelier David
___
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: editors/vim installs to /

[David DEMELIER]

2010/9/17 jhell :
>
> After a force upgrade of vim that had failed unfortunately not
> registering the files it installed already I found out that it is
> installing to / ~! ugh.
>
> Why is ${PREFIX} being used and not ${LOCALBASE} ???
>
> --
>
>  jhell,v
> ___
> 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"
>

No,

${PREFIX} is the good variable to specify the installation directory,
of course if you set this the port will probably install its files in
the user-defined ${PREFIX}.

I'm writing the rewrite of the port to update vim to 7.3 and with a
real OPTIONS framework and remove the stupid WITH_VIM_OPTIONS KNOB
that doesn't work. The problem is that David doesn't like clean things
and I think he won't commit it because it won't be enough complicated.

With kind regards,

-- 
Demelier David
___
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: editors/vim installs to /

[David DEMELIER]

2010/9/19 David O'Brien :
> On Fri, Sep 17, 2010 at 09:21:46PM +0200, David DEMELIER wrote:
>> I'm writing the rewrite of the port to update vim to 7.3 and with a
>> real OPTIONS framework and remove the stupid WITH_VIM_OPTIONS KNOB
>> that doesn't work.  The problem is that David doesn't like clean things
>> and I think he won't commit it because it won't be enough complicated.
>
> No I won't commit it - I do like clean things I don't find OPTIONS to be
> sufficiently clean.  So please don't waste your time and mine.  If you
> have improvements (other than removing WITH_VIM_OPTIONS), please do send
> those in.
>

What is "sufficiently clean" ? I wonder what is not clean in the
options framework, so please tell me then we still can clean it?

-- 
Demelier David
___
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"

x11/sessreg fails to build

[David DEMELIER]

Hello,

Fetched ports today :

===>  Building for sessreg-1.0.5_1
/usr/bin/make  all-am
cc -std=gnu99 -DHAVE_CONFIG_H -I. -Wall -Wpointer-arith
-Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations
-Wnested-externs -fno-strict-aliasing -Wbad-function-cast -Wformat=2
-Wold-style-definition -Wdeclaration-after-statement
-I/usr/local/include -O2 -pipe -fno-strict-aliasing -MT sessreg.o -MD
-MP -MF .deps/sessreg.Tpo -c -o sessreg.o sessreg.c
mv -f .deps/sessreg.Tpo .deps/sessreg.Po
cc -std=gnu99 -Wall -Wpointer-arith -Wstrict-prototypes
-Wmissing-prototypes -Wmissing-declarations -Wnested-externs
-fno-strict-aliasing -Wbad-function-cast -Wformat=2
-Wold-style-definition -Wdeclaration-after-statement
-I/usr/local/include -O2 -pipe -fno-strict-aliasing   -o sessreg
sessreg.o
sessreg.o(.text+0xfa): In function `UtmpxIdOpen':
: undefined reference to `setutxent'
sessreg.o(.text+0x101): In function `UtmpxIdOpen':
: undefined reference to `getutxent'
sessreg.o(.text+0x12b): In function `UtmpxIdOpen':
: undefined reference to `endutxent'
sessreg.o(.text+0x13b): In function `UtmpxIdOpen':
: undefined reference to `endutxent'
sessreg.o(.text+0x992): In function `main':
: undefined reference to `setutxent'
sessreg.o(.text+0x99f): In function `main':
: undefined reference to `getutxid'
sessreg.o(.text+0x9ac): In function `main':
: undefined reference to `pututxline'
sessreg.o(.text+0x9b1): In function `main':
: undefined reference to `endutxent'
sessreg.o(.text+0xa91): In function `main':
: undefined reference to `getutxent'
sessreg.o(.text+0xace): In function `main':
: undefined reference to `endutxent'
*** Error code 1

Stop in /usr/obj/usr/ports/x11/sessreg/work/sessreg-1.0.5.
*** Error code 1

Stop in /usr/obj/usr/ports/x11/sessreg/work/sessreg-1.0.5.
*** Error code 1


-- 
Demelier David
___
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: x11/sessreg fails to build

[David DEMELIER]

2010/9/22 Anonymous :
> David DEMELIER  writes:
>
>> sessreg.o(.text+0xfa): In function `UtmpxIdOpen':
>> : undefined reference to `setutxent'
>> sessreg.o(.text+0x101): In function `UtmpxIdOpen':
>> : undefined reference to `getutxent'
>> sessreg.o(.text+0x12b): In function `UtmpxIdOpen':
>> : undefined reference to `endutxent'
>> sessreg.o(.text+0x13b): In function `UtmpxIdOpen':
>> : undefined reference to `endutxent'
>> sessreg.o(.text+0x992): In function `main':
>> : undefined reference to `setutxent'
>> sessreg.o(.text+0x99f): In function `main':
>> : undefined reference to `getutxid'
>> sessreg.o(.text+0x9ac): In function `main':
>> : undefined reference to `pututxline'
>> sessreg.o(.text+0x9b1): In function `main':
>> : undefined reference to `endutxent'
>> sessreg.o(.text+0xa91): In function `main':
>> : undefined reference to `getutxent'
>> sessreg.o(.text+0xace): In function `main':
>> : undefined reference to `endutxent'
>> *** Error code 1
>
> Do you have utmpx.h in /usr/include while not having getutxent(3) in libc?
> I guess this may happen if you downgrade from /head to /stable/8.
>
> If it's smth else providing config.log is essential.
>

 74 __BEGIN_DECLS
 75 voidendutxent(void);
 76 struct utmpx *getutxent(void);
 77 struct utmpx *getutxid(const struct utmpx *);
 78 struct utmpx *getutxline(const struct utmpx *);
 79 struct utmpx *pututxline(const struct utmpx *);
 80 voidsetutxent(void);
 81

I have them in /usr/include/utmpx.h

At configure stage :

checking utmpx.h usability... yes
checking utmpx.h presence... yes
checking for utmpx.h... yes

In config.log there is not something strange but if you want to check
it I attached it.

By the way I'm running 8.1-RELEASE on amd64.

With kind regards,

-- 
Demelier David


config.log
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: x11/sessreg fails to build

[David DEMELIER]

2010/9/22 Anonymous :
> David DEMELIER  writes:
>
>> I have them in /usr/include/utmpx.h
>>
>> At configure stage :
>>
>> checking utmpx.h usability... yes
>> checking utmpx.h presence... yes
>> checking for utmpx.h... yes
>>
>> In config.log there is not something strange but if you want to check
>> it I attached it.
>>
>> By the way I'm running 8.1-RELEASE on amd64.
>
> There is no utmpx.h on 8.1-RELEASE.
>

Then it's there because I downgraded from -STABLE, then I should
remove it safely ?

-- 
Demelier David
___
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: x11/sessreg fails to build

[David DEMELIER]

2010/9/22 David Wolfskill :
> On Wed, Sep 22, 2010 at 08:52:02PM +0200, David DEMELIER wrote:
>> 
>> > There is no utmpx.h on 8.1-RELEASE.
>> >
>>
>> Then it's there because I downgraded from -STABLE, then I should
>> remove it safely ?
>
> When I do a source upgrade (which I do way more frequently than is
> sane), I augment the instructions in /usr/src/UPDATING so that just
> after "make installkernel", I run "mergemaster -p" (as specified),
> then move /usr/include aside prior to "make installworld": the "make
> installworld" will re-populate /usr/include afresh, and that way I
> know it doesn't contain anything it's not supposed to.
>
> Peace,
> david
> --
> David H. Wolfskill                              da...@catwhisker.org
> Depriving a girl or boy of an opportunity for education is evil.
>
> See http://www.catwhisker.org/~david/publickey.gpg for my public key.
>

I finally just rm /usr/include/utmpx.h and it worked. Sorry for my
mistakes. I won't downgrade a system again without cleaning
everything.

Cheers,

-- 
Demelier David
___
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: Web feed for /usr/ports/UPDATING

[David DEMELIER]

2010/9/24 Jason :
> On Fri, Sep 24, 2010 at 08:16:53PM +0200, Michal Varga thus spake:
>>
>> On Fri, 2010-09-24 at 11:08 -0700, Charlie Kester wrote:
>>>
>>> On Thu 23 Sep 2010 at 20:39:25 PDT Alexander Kojevnikov wrote:
>>> >Hi list,
>>> >
>>> >Since the only SUBJ I could find [0] is long since dead I created my
>>> > own:
>>> >
>>> >http://updating.versia.com/
>>> >
>>> >Any feedback is welcome.
>>>
>>> Cool idea!  Count me as another subscriber.
>>
>>
>> +1, Subscribed
>
> I subscribed, as well. It would be great to get this code working inside the
> Documentation Project, itself, and serve the feed from:
>
> http://www.freebsd.org/ports/updating.html
>
>>
>>
>> --
>> 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"
>

Love, love and love !

Kind regards,

-- 
Demelier David
___
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"

Can't compile x11/hs-X11-xft

[David DEMELIER]

Hi,

Today I can't compile xmonad-contrib anymore (hs-X11-xft is failing)

===>  Installing for hs-xmonad-0.9.1_1
===>   hs-xmonad-0.9.1_1 depends on executable: ghc - found
===>   hs-xmonad-0.9.1_1 depends on package: hs-X11>=1.5.0.0 - found
===>   hs-xmonad-0.9.1_1 depends on file:
/usr/local/libdata/pkgconfig/x11.pc - found
===>   Generating temporary packing list
===>  Checking if x11-wm/hs-xmonad already installed
Installing library in /usr/local/lib/xmonad-0.9.1/ghc-6.10.4
Installing executable(s) in /usr/local/bin
Registering xmonad-0.9.1...
Reading package info from "dist/installed-pkg-config" ... done.
Writing new package config file... done.
===>   Compressing manual pages for hs-xmonad-0.9.1_1
===>   Registering installation for hs-xmonad-0.9.1_1
===>   Returning to build of hs-xmonad-contrib-0.9.1_1
===>   hs-xmonad-contrib-0.9.1_1 depends on package: hs-utf8-string>=0 - found
===>   hs-xmonad-contrib-0.9.1_1 depends on package: hs-X11-xft>=0.2 - not found
===>Verifying install for hs-X11-xft>=0.2 in /usr/ports/x11/hs-X11-xft
===>  Vulnerability check disabled, database not found
===>  License check disabled, port has not defined LICENSE
===>  Extracting for hs-X11-xft-0.3_4
=> MD5 Checksum OK for cabal/X11-xft-0.3.tar.gz.
=> SHA256 Checksum OK for cabal/X11-xft-0.3.tar.gz.
===>  Patching for hs-X11-xft-0.3_4
===>   hs-X11-xft-0.3_4 depends on executable: ghc - found
===>   hs-X11-xft-0.3_4 depends on package: hs-utf8-string>=0.1 - found
===>   hs-X11-xft-0.3_4 depends on package: hs-X11>=1.2.1 - found
===>   hs-X11-xft-0.3_4 depends on executable: haddock - found
===>   hs-X11-xft-0.3_4 depends on executable: HsColour - found
===>   hs-X11-xft-0.3_4 depends on file:
/usr/local/libdata/pkgconfig/xft.pc - found
===>   hs-X11-xft-0.3_4 depends on file:
/usr/local/libdata/pkgconfig/xrender.pc - found
===>  Configuring for hs-X11-xft-0.3_4
[1 of 1] Compiling Main ( Setup.lhs, Setup.o )
Linking setup ...
Configuring X11-xft-0.3...
setup: At least the following dependencies are missing:
utf8-string >=0.1
*** Error code 1

Stop in /usr/ports/x11/hs-X11-xft.
*** Error code 1

Stop in /usr/ports/x11-wm/hs-xmonad-contrib.
*** Error code 1

Stop in /usr/ports/x11-wm/hs-xmonad-contrib.

mark...@melon ...x11-wm/hs-xmonad-contrib $ pkg_info hs-utf8-string-0.3.6
Information for hs-utf8-string-0.3.6:
[...]

I don't know what is happening right now.

-- 
Demelier David
___
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: Can't compile x11/hs-X11-xft

[David DEMELIER]

2010/9/25 jhell :
> On 09/25/2010 13:54, David DEMELIER wrote:
>> Hi,
>>
>> Today I can't compile xmonad-contrib anymore (hs-X11-xft is failing)
>>
>> ===>  Installing for hs-xmonad-0.9.1_1
>> ===>   hs-xmonad-0.9.1_1 depends on executable: ghc - found
>> ===>   hs-xmonad-0.9.1_1 depends on package: hs-X11>=1.5.0.0 - found
>> ===>   hs-xmonad-0.9.1_1 depends on file:
>> /usr/local/libdata/pkgconfig/x11.pc - found
>> ===>   Generating temporary packing list
>> ===>  Checking if x11-wm/hs-xmonad already installed
>> Installing library in /usr/local/lib/xmonad-0.9.1/ghc-6.10.4
>> Installing executable(s) in /usr/local/bin
>> Registering xmonad-0.9.1...
>> Reading package info from "dist/installed-pkg-config" ... done.
>> Writing new package config file... done.
>> ===>   Compressing manual pages for hs-xmonad-0.9.1_1
>> ===>   Registering installation for hs-xmonad-0.9.1_1
>> ===>   Returning to build of hs-xmonad-contrib-0.9.1_1
>> ===>   hs-xmonad-contrib-0.9.1_1 depends on package: hs-utf8-string>=0 - 
>> found
>> ===>   hs-xmonad-contrib-0.9.1_1 depends on package: hs-X11-xft>=0.2 - not 
>> found
>> ===>    Verifying install for hs-X11-xft>=0.2 in /usr/ports/x11/hs-X11-xft
>> ===>  Vulnerability check disabled, database not found
>> ===>  License check disabled, port has not defined LICENSE
>> ===>  Extracting for hs-X11-xft-0.3_4
>> => MD5 Checksum OK for cabal/X11-xft-0.3.tar.gz.
>> => SHA256 Checksum OK for cabal/X11-xft-0.3.tar.gz.
>> ===>  Patching for hs-X11-xft-0.3_4
>> ===>   hs-X11-xft-0.3_4 depends on executable: ghc - found
>> ===>   hs-X11-xft-0.3_4 depends on package: hs-utf8-string>=0.1 - found
>> ===>   hs-X11-xft-0.3_4 depends on package: hs-X11>=1.2.1 - found
>> ===>   hs-X11-xft-0.3_4 depends on executable: haddock - found
>> ===>   hs-X11-xft-0.3_4 depends on executable: HsColour - found
>> ===>   hs-X11-xft-0.3_4 depends on file:
>> /usr/local/libdata/pkgconfig/xft.pc - found
>> ===>   hs-X11-xft-0.3_4 depends on file:
>> /usr/local/libdata/pkgconfig/xrender.pc - found
>> ===>  Configuring for hs-X11-xft-0.3_4
>> [1 of 1] Compiling Main             ( Setup.lhs, Setup.o )
>> Linking setup ...
>> Configuring X11-xft-0.3...
>> setup: At least the following dependencies are missing:
>> utf8-string >=0.1
>> *** Error code 1
>>
>> Stop in /usr/ports/x11/hs-X11-xft.
>> *** Error code 1
>>
>> Stop in /usr/ports/x11-wm/hs-xmonad-contrib.
>> *** Error code 1
>>
>> Stop in /usr/ports/x11-wm/hs-xmonad-contrib.
>>
>> mark...@melon ...x11-wm/hs-xmonad-contrib $ pkg_info hs-utf8-string-0.3.6
>> Information for hs-utf8-string-0.3.6:
>> [...]
>>
>> I don't know what is happening right now.
>>
>
> These are part of the rest of the hs-* ports. They usually have to be
> compiled in order to compile correctly against their brothers and
> sisters. What usually solves this for me is ( portmaster hs-\* ).
>
>
> Good luck,
>
> --
>
>  jhell,v
>

Maybe hs-utf8-string-0.3.6 was misinstalled, I pkg_delete'd -f it and
it works now. Sorry for the noise

-- 
Demelier David
___
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"

Create bootstrap binaries for openjdk

[David DEMELIER]

Hello,

For people who try to install openjdk, they saw that we need to
install an other available jdk like diablo-jdk which is really painful
to install from ports since we need to fetch one million of distfiles
manually.

What NetBSD' pkgsrc done is making availables binaries for
bootstrapping, I would propose this idea too then the port will not
depend on the non-free and painful diablo-jdk.

Bootstrap binaries should be done for FreeBSD 7.x release and 8.x
release for i386 and amd64 architecture, then the port will be able to
download the bootstrap binaries from official FreeBSD ftp servers.

I like much this idea, and if you agree on I will send a PR with
patches for it, but since I don't have FreeBSD 7.x version I would
like someone to make binaries for i386 and amd64.

With kind regards,

-- 
Demelier David
___
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: Web feeds for UPDATING files

[David DEMELIER]

2010/9/25 jhell :
> On 09/25/2010 09:24, Alexander Kojevnikov wrote:
>> On 25 September 2010 17:04, Alexander Kojevnikov
>>  wrote:
>>> On 25 September 2010 15:44, jhell  wrote:
 Really awesome!

 This will come in handy to serve up stable/*/UPDATING and head/UPDATING
 to. And thinking along those lines it could probably be incorporated
 directly into the DAV tree on svn. to serve directly from there.
>>>
>>> Great idea, I'll try to implement both feeds during the weekend and
>>> will post here and on freebsd-current@ and freebsd-stable@ when it's
>>> done.
>>
>> ...and done:
>>
>> http://updating.versia.com/
>>
>> The site now features Atom feeds for the following files:
>>
>> * ports/UPDATING
>> * head/UPDATING
>> * stable/7/UPDATING
>> * stable/8/UPDATING
>>
>> Hope you find the feeds useful.
>>
>> Cheers,
>> Alex
>>
>> PS: I apologise to ports/UPDATING subscribers who got quite a few
>> duplicate entries. I barely missed the Ballmer Peak, just delete
>> those.
>
> Your amazing!
>
> Thanks Alexander!
>
> --
>
>  jhell,v
> ___
> freebsd-sta...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>

It's so great that it should be merge to the official FreeBSD web page!

Thanks a lot!

Kind regards,

-- 
Demelier David
___
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"

Failure to build emulators/vba with WITH_GTK2 knob

[David DEMELIER]

Hi,

I think the gtk contrib in vba is broken :

if c++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\"
-DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\"
-DPACKAGE=\"VisualBoyAdvance\" -DVERSION=\"1.7.2\" -DYYTEXT_POINTER=1
-DHAVE_LIBZ=1 -DHAVE_LIBPNG=1 -DHAVE_LIBPTHREAD=1 -DSTDC_HEADERS=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1
-DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1
-DHAVE_STRINGS_H=1 -DHAVE_UNISTD_H=1 -DHAVE_ARPA_INET_H=1
-DHAVE_NETINET_IN_H=1 -DHAVE_ICONV=1 -DENABLE_NLS=1 -DHAVE_GETTEXT=1
-DHAVE_DCGETTEXT=1 -DHAVE_LIBINTL_H=1  -I. -I.
-DPKGDATADIR=\"/usr/local/share/VisualBoyAdvance\"
-DLOCALEDIR=\"/usr/local/share/locale\"
-DGETTEXT_PACKAGE=\"vba-1.7.2\"  -I/usr/local/include -D_REENTRANT
-D_THREAD_SAFE -I/usr/local/include/gtkmm-2.4
-I/usr/local/lib/gtkmm-2.4/include -I/usr/local/include/giomm-2.4
-I/usr/local/lib/giomm-2.4/include -I/usr/local/include/pangomm-1.4
-I/usr/local/lib/pangomm-1.4/include -I/usr/local/include/gtk-2.0
-I/usr/local/include/gtk-unix-print-2.0 -I/usr/local/include/atkmm-1.6
-I/usr/local/include/gdkmm-2.4 -I/usr/local/lib/gdkmm-2.4/include
-I/usr/local/include/glibmm-2.4 -I/usr/local/lib/glibmm-2.4/include
-I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include
-I/usr/local/include/sigc++-2.0 -I/usr/local/lib/sigc++-2.0/include
-I/usr/local/include/cairomm-1.0 -I/usr/local/lib/cairomm-1.0/include
-I/usr/local/include/pango-1.0 -I/usr/local/include/cairo
-I/usr/local/include/pixman-1 -I/usr/local/include/freetype2
-I/usr/local/include -I/usr/local/lib/gtk-2.0/include
-I/usr/local/include/atk-1.0 -I/usr/local/include/gio-unix-2.0/
-I/usr/local/include/libglademm-2.4
-I/usr/local/lib/libglademm-2.4/include
-I/usr/local/include/libglade-2.0 -I/usr/local/include/libxml2
-I/usr/local/include/SDL -I/usr/local/include -D_GNU_SOURCE=1
-D_REENTRANT -O2 -pipe -fno-strict-aliasing -DC_CORE -DDEV_VERSION -MT
gvba-joypadconfig.o -MD -MP -MF ".deps/gvba-joypadconfig.Tpo" \
  -c -o gvba-joypadconfig.o `test -f 'joypadconfig.cpp' || echo
'./'`joypadconfig.cpp; \
then mv -f ".deps/gvba-joypadconfig.Tpo" ".deps/gvba-joypadconfig.Po"; \
else rm -f ".deps/gvba-joypadconfig.Tpo"; exit 1; \
fi
In file included from joypadconfig.h:29,
 from joypadconfig.cpp:19:
sigccompat.h:35: error: expected initializer before '<' token
sigccompat.h:41: error: expected initializer before '<' token
sigccompat.h:47: error: expected initializer before '<' token
joypadconfig.cpp: In constructor
'VBA::JoypadConfigDialog::JoypadConfigDialog(GtkDialog*, const
Glib::RefPtr&)':
joypadconfig.cpp:167: error: 'bind' is not a member of 'SigC'
joypadconfig.cpp:167: error: expected primary-expression before '>' token
joypadconfig.cpp:168: error: 'slot' is not a member of 'SigC'
joypadconfig.cpp:170: error: 'slot' is not a member of 'SigC'
gmake[3]: *** [gvba-joypadconfig.o] Error 1
gmake[3]: Leaving directory
`/usr/obj/usr/ports/emulators/vba/work/VisualBoyAdvance-1.7.2/src/gtk'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory
`/usr/obj/usr/ports/emulators/vba/work/VisualBoyAdvance-1.7.2/src/gtk'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory
`/usr/obj/usr/ports/emulators/vba/work/VisualBoyAdvance-1.7.2/src'
gmake: *** [all-recursive] Error 1
*** Error code 1

Stop in /usr/ports/emulators/vba.

This happens on 8.1-STABLE amd64.

Maybe we should add a BROKEN= statement?

Cheers,

-- 
Demelier David
___
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: OPTIONS (was: editors/vim installs to /)

[David DEMELIER]

2010/10/2 David O'Brien :
> On Sun, Sep 19, 2010 at 10:24:59AM +0200, David DEMELIER wrote:
>> What is "sufficiently clean" ? I wonder what is not clean in the
>> options framework, so please tell me then we still can clean it?
>
> When the Ports Collection was invented, ports maintainers were to
> choose a reasonable set of configuration for the FreeBSD community
> and have the port build that way.
>
> Today we have ports that seem to expose every single option to GNU
> configure and giving the user a puzzling choice of too many things.
> Often the explanations are nothing more than restating the option
> name and the user is left wondering what is X?  What does Y mean?
> How do I know if I really want Z or not?  Why is threading so often
> an OPTION and not just the default?  Why do I have to go read the
> packages README and INSTALLING to figure out the caveats of say
> enabling threading?  Or what the other list of things are and their
> caveats?
>
> 1. One should not have to deal with the OPTIONS dialog just to
> 'make extract' if one wants to check the license or otherwise
> investigate a port before deciding to install it.
>
> 2. With the way OPTIONS handling is done, there isn't a way for me
> to query if I built with the defaults or not.
> Thus leading to every port I manually install looking like it was
> customized just because /var/db/ports/${PORTNAME} exists.  Thus
> implying I can no longer install the pre-build package.
>

make rmconfig ?

> 3. OPTIONS are limited to only checkbox YES/NO settings.
> Why can I not set PREFIX thru the OPTIONS framework and have it come
> from /var/db/ports/${PORTNAME}/options on the 2nd and later builds?
> Even the boolean NOPORTDOCS isn't available thru OPTIONS.
> Thus it is an inconsistent way to configure a port.
>

I agree. As I said in 4, OPTIONS should follow the defined knob in
make.conf. But for not boolean knobs there is something we can also
do, spawn a little textbox to define an option with a string. Example
:

[X] WITH_X foo bar
[ ] WITH_Y foo bar baz
[fr_FR en_GB] LANGS to be build

Here pressing enter on LANGS would spawn a little textbox that can be
fulfilled by the user. The little problem is how to tell to OPTIONS
that it's not a boolean entry.

> 4. When I build misc/mc-light and have "WITHOUT_NLS=yes" in
> /etc/make.conf, why does the OPTIONS dialog offer me
> "[X] NLS Enable gettext support" instead of defaulting the
> dialog to unchecked?
>

I agree with this inconsistency, I think with a little of work OPTIONS
framework should be to follow KNOB to enable an option if it's already
defined by the user. This would be great for people that use
WITHOUT_GNOME, WITHOUT_X11 and so on. I think it's possible to do it.

pkgsrc do it with PKG_DEFAULT_OPTIONS= setting.

> 5. One cannot opt-out of OPTIONS.
> WITHOUT_OPTIONS does not work to just get the defaults while skipping
> the OPTIONS dialog.  Note, setting BATCH does a lot more than just
> make OPTIONS non-interactive (for some ports it stops other
> non-OPTIONS interaction with the user that one should see).  Thus
> there is no way to get an uninterrupted default build of something.
>
> 6. One cannot opt-in/opt-out on a per-port basis.
> WITH[OUT]_${PORTNAME}_OPTIONS and ${PORTNAME}_WITH[OUT]_OPTIONS
> should be supported to control the OPTIONS dialog just when
> building ${PORTNAME}.
>
> 7. Setting ${PORTNAME}_WITH[OUT]_ (or
> WITH[OUT]_${PORTNAME}_) should set
> WITH[OUT]_ just when building ${PORTNAME}.
> So that folks who don't want to be interrupted with OPTIONS every
> time there is an update to the list can hardcode their choices in
> /etc/make.conf.
>

Yes, check my answer at 4.

> 8. OPTIONS make a mess in the typescript file from
> 'script typescript make', and the choices are totally unreadable vs.
> 'script typescript make -DWITH_FOO -WITHOUT_BAR'.
>

There is a disadvantages with knobs here, you must define knob each
time you install/upgrade a port. Of course you can do it with the
make.conf or the portconf system.

OPTIONS also prints -DSOMETHING when compiling.

Definitely, I like knobs and I like options. But mixing the both is
painful. You should check by typing make config or sometime lsknobs or
even reading the makefile.

The best thing to do is switch totally to a way to configure a port
and remove the other one. I think we should try to upgrade the options
framework with what I said at 4. and 3. It's possible but we need some
work.

Kind regards,

-- 
Demelier David
___
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: OPTIONS

[David DEMELIER]

2010/10/3 Matthew Seaman :
> On 03/10/2010 09:22:46, David DEMELIER wrote:
>>> 3. OPTIONS are limited to only checkbox YES/NO settings.
>>> > Why can I not set PREFIX thru the OPTIONS framework and have it come
>>> > from /var/db/ports/${PORTNAME}/options on the 2nd and later builds?
>>> > Even the boolean NOPORTDOCS isn't available thru OPTIONS.
>>> > Thus it is an inconsistent way to configure a port.
>>> >
>> I agree. As I said in 4, OPTIONS should follow the defined knob in
>> make.conf. But for not boolean knobs there is something we can also
>> do, spawn a little textbox to define an option with a string. Example
>> :
>>
>> [X] WITH_X foo bar
>> [ ] WITH_Y foo bar baz
>> [fr_FR en_GB] LANGS to be build
>>
>> Here pressing enter on LANGS would spawn a little textbox that can be
>> fulfilled by the user. The little problem is how to tell to OPTIONS
>> that it's not a boolean entry.
>>
>
> And the rest?  Pursuing this idea through to its logical conclusion,
> you'ld end up implementing radio buttons, text entry boxes, drop down
> lists -- all the normal bits used in html forms.
>

Don't you like this? sysinstall was made with dialog. And radiobuttons
could be used to choose a group of options yes, for example when you
only need to choose one option in three available choices, then BROKEN
lines could be removed :-)

> In fact, you might just as well write a small HTML form, display it
> using lynx or w3c or some other text mode browser[*], and then have the
> form action feed into a CGI program that outputs a small Makefile with
> appropriate variable definitions in it.
>

I don't want something complex, checkbox, textbox, radiobuttons is enough.

> Hmmm... doesn't address David's point about options dialogs not showing
> pre-existing options settings, but it should be simple enough to have a
> 'Use default settings' check box.
>
>        Cheers,
>
>        Matthew
>
> [*] Or FF if you really must.
>
> --
> Dr Matthew J Seaman MA, D.Phil.                   7 Priory Courtyard
>                                                  Flat 3
> PGP: http://www.infracaninophile.co.uk/pgpkey     Ramsgate
> JID: matt...@infracaninophile.co.uk               Kent, CT11 9PW
>
>



-- 
Demelier David
___
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: OPTIONS

[David DEMELIER]

2010/10/3 Dominic Fandrey :
> On 03/10/2010 11:45, David DEMELIER wrote:
>> 2010/10/3 Matthew Seaman :
>> I don't want something complex, checkbox, textbox, radiobuttons is enough.
>
> Textbox is _very_ complex. Think of all the code you'd have to
> add to ports to check what was entered by the user.
> At the very least you have to verify that whatever was provided
> is valid. For the feature not to become annoying you'd have to
> be a lot more fuzzy and complex, though.
>

What do you mean by valid? In the way that the user can't insert any
no alpha-numeric characters or an entry that is only valid to the
application ?

-- 
Demelier David
___
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"

openoffice.org-3 does not build anymore

[David DEMELIER]

Hi,

I can't build openoffice.org-3 anymore,

readlicense_oo
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /usr/obj/usr/ports/editors/openoffice.o
rg-3/work/OOO320_m19/readlicense_oo/

Attention: if you build and deliver the above module(s) you may prolongue your t
he build issuing command "build --from readlicense_oo"

rmdir /tmp/aTcGY4w2lp
*** Error code 1

Stop in /usr/ports/editors/openoffice.org-3.

Cheers,

-- 
Demelier David
___
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: OPTIONS

[David DEMELIER]

2010/10/3 Dominic Fandrey :
> On 03/10/2010 12:29, David DEMELIER wrote:
>> 2010/10/3 Dominic Fandrey :
>>> On 03/10/2010 11:45, David DEMELIER wrote:
>>>> 2010/10/3 Matthew Seaman :
>>>> I don't want something complex, checkbox, textbox, radiobuttons is enough.
>>>
>>> Textbox is _very_ complex. Think of all the code you'd have to
>>> add to ports to check what was entered by the user.
>>> At the very least you have to verify that whatever was provided
>>> is valid. For the feature not to become annoying you'd have to
>>> be a lot more fuzzy and complex, though.
>>>
>>
>> What do you mean by valid? In the way that the user can't insert any
>> no alpha-numeric characters or an entry that is only valid to the
>> application ?
>>
>
> Text fields are arbitrary and you'd probably want to limit it to
> a specific purpose, like a list of languages.
>
> So is de_* an acceptable language? Do you delimit with space, pipe
> or semicolon? Do people really want to be bothered with learning
> the specific syntax of your ports text input fields?
>

In the openoffice ports you have LOCALIZED_LANG knob, I needed to
check which kind of delimiters was needed and it's a space, so delimit
by space is enough.

-- 
Demelier David
___
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: OPTIONS

[David DEMELIER]

2010/10/3 Matthew Seaman :
> On 03/10/2010 10:45:01, David DEMELIER wrote:
>> 2010/10/3 Matthew Seaman :
>>> On 03/10/2010 09:22:46, David DEMELIER wrote:
>>>>> 3. OPTIONS are limited to only checkbox YES/NO settings.
>>>>>> Why can I not set PREFIX thru the OPTIONS framework and have it come
>>>>>> from /var/db/ports/${PORTNAME}/options on the 2nd and later builds?
>>>>>> Even the boolean NOPORTDOCS isn't available thru OPTIONS.
>>>>>> Thus it is an inconsistent way to configure a port.
>>>>>>
>>>> I agree. As I said in 4, OPTIONS should follow the defined knob in
>>>> make.conf. But for not boolean knobs there is something we can also
>>>> do, spawn a little textbox to define an option with a string. Example
>>>> :
>>>>
>>>> [X] WITH_X foo bar
>>>> [ ] WITH_Y foo bar baz
>>>> [fr_FR en_GB] LANGS to be build
>>>>
>>>> Here pressing enter on LANGS would spawn a little textbox that can be
>>>> fulfilled by the user. The little problem is how to tell to OPTIONS
>>>> that it's not a boolean entry.
>>>>
>>>
>>> And the rest?  Pursuing this idea through to its logical conclusion,
>>> you'ld end up implementing radio buttons, text entry boxes, drop down
>>> lists -- all the normal bits used in html forms.
>>>
>>
>> Don't you like this? sysinstall was made with dialog. And radiobuttons
>> could be used to choose a group of options yes, for example when you
>> only need to choose one option in three available choices, then BROKEN
>> lines could be removed :-)
>
> Don't get me wrong -- I think the current OPTIONS processing is at once
> too limited and too intrusive, and that it is ripe for some serious
> improvement.  I'm all for your idea; I just don't think you've gone far
> enough.
>
> Now, personally, I quite like the idea of simply sticking entries into
> /etc/make.conf to control port compilation settings.  Which would be
> fine for me managing my small number of home machines, but certainly not
> suitable for all users.  There is also the problem of knowing what
> controls are available and having some reasonable idea of what they do,
> without the necessity of being a make(1) guru or grovelling through the
> guts of dozens of ports.
>

Yes that's why I would like that OPTIONS must read make.conf to set
default ports options and only after make a individual change for it.

> Giving OPTIONS processing a lot more flexibility, and the capability to
> display help text etc. (yes -- I know there have been attempts in this
> direction already) plus pushing some of the logic up from the Makefile
> into the OPTIONS dialogue[*] would certainly improve the user experience.
>
> Something with the capabilities of sysinstall would be a step in the
> right direction, but I think most would agree, sysinstall is a bit
> clunky and confusing to new users.  An alternative that behaves like a
> web form is going to be a lot more accessible to J. Random User.
>
> But that is really beyond the limits of what I have any idea about
> coding.  I can see how to prototype it readily enough as a web app, but
> having to fire up an instance of apache or something just to install a
> few ports just ain't right.
>
>        Cheers,
>
>        Matthew
>
> [*] Ever had the experience of clicking on OPTIONS settings and then
> finding the port won't accept that combination of OPTIONS?  That's
> frustrating, especially when combined with the use of eg. portmaster(8)
> where choosing OPTIONS can happen quite a while before attempting to
> build the port.
>
> --
> Dr Matthew J Seaman MA, D.Phil.                   7 Priory Courtyard
>                                                  Flat 3
> PGP: http://www.infracaninophile.co.uk/pgpkey     Ramsgate
> JID: matt...@infracaninophile.co.uk               Kent, CT11 9PW
>
>



-- 
Demelier David
___
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: openoffice.org-3 does not build anymore

[David DEMELIER]

2010/10/3 ajtiM :
> On Sunday 03 October 2010 05:40:33 David DEMELIER wrote:
>> Hi,
>>
>> I can't build openoffice.org-3 anymore,
>>
>>         readlicense_oo
>> need(s) to be rebuilt
>>
>> Reason(s):
>>
>> ERROR: error 65280 occurred while making
>> /usr/obj/usr/ports/editors/openoffice.o
>> rg-3/work/OOO320_m19/readlicense_oo/
>>
>> Attention: if you build and deliver the above module(s) you may prolongue
>> your t he build issuing command "build --from readlicense_oo"
>>
>> rmdir /tmp/aTcGY4w2lp
>> *** Error code 1
>>
>> Stop in /usr/ports/editors/openoffice.org-3.
>>
>> Cheers,
>
> I didn't have problem with RC-3 and it works very good (started yesterday
> about eight in the evening and it is done).
>
> Mitja
> 
> http://starikarp.redbubble.com
>

So I don't understand.

-- 
Demelier David
___
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: OPTIONS (was: editors/vim installs to /)

[David DEMELIER]

2010/10/5 David O'Brien :
> On Sun, Oct 03, 2010 at 10:22:46AM +0200, David DEMELIER wrote:
>> 2010/10/2 David O'Brien :
>> > 2. With the way OPTIONS handling is done, there isn't a way for me
>> > to query if I built with the defaults or not.
>> > Thus leading to every port I manually install looking like it was
>> > customized just because /var/db/ports/${PORTNAME} exists.  Thus
>> > implying I can no longer install the pre-build package.
>>
>> make rmconfig ?
>
> I think you've missed my point.
>
> That does not tell me if I, in the past, made a decision that did not
> like the maintainer's defaults, or if I just wanted to extract the
> sources so I could read the license or figure out what the OPTIONS knobs
> were about, etc..
>

I understood, you prefere a file like make.conf or ports.conf to see
which options/knob is defined, isn't it ?

>> The best thing to do is switch totally to a way to configure a port
>> and remove the other one.
>
> Only if folks agree on what the best way to configure a port is.
> I spoke with some co-workers last week, and OPTIONS weren't very
> popular with them.  They also stated some of the the issues I listed.
>
>
>> I think we should try to upgrade the options
>> framework with what I said at 4. and 3. It's possible but we need some
>> work.
>
> Even without forcing all ports to go in one direction for configuration,
> this would be a Good Thing to do.  Hopefully someone with interest will
> submit some patches.
>

I will try to do it, I think a replacement of ports.conf with a make
syntax would be better. I will try to do something in the end of week.

> --
> -- David  (obr...@freebsd.org)
> Q: Because it reverses the logical flow of conversation.
> A: Why is top-posting (putting a reply at the top of the message) frowned 
> upon?
> Let's not play "Jeopardy-style quoting"
> ___
> 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"
>

Kind regards,

-- 
Demelier David
___
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"

Users needed or not by ports

[David DEMELIER]

Hello,

Before writing a patch for the ports framework, I just want to be sure
that FreeBSD ports shouldn't use a same user added by ports. For
example pulseaudio adds some users to the system (pulse,
pulse-whatever) and should these users be needed from others ports ?

My plan is :

1. Register users added and needed by ports in files like +USERS +GROUPS,
2. When make deinstall or pkg_delete port_name check if the user is
still needed by other port (if this is possible)
3. Print a message like "The following users and group are not needed
anymore by the system : xxx yyy"

pkgsrc already use something like this, so a port should be really
easy to be done.

-- 
Demelier David
___
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: Users needed or not by ports

[David DEMELIER]

2010/10/12 Florent Thoumie :
> On Mon, Oct 11, 2010 at 5:01 PM, David DEMELIER
>  wrote:
>> Hello,
>>
>> Before writing a patch for the ports framework, I just want to be sure
>> that FreeBSD ports shouldn't use a same user added by ports. For
>> example pulseaudio adds some users to the system (pulse,
>> pulse-whatever) and should these users be needed from others ports ?
>>
>> My plan is :
>>
>> 1. Register users added and needed by ports in files like +USERS +GROUPS,
>> 2. When make deinstall or pkg_delete port_name check if the user is
>> still needed by other port (if this is possible)
>> 3. Print a message like "The following users and group are not needed
>> anymore by the system : xxx yyy"
>>
>> pkgsrc already use something like this, so a port should be really
>> easy to be done.
>
> This has already been discussed (including in a thread that you started [1]).
>
> This needs support in both ports and pkg_install.
>
> [1] http://www.mail-archive.com/freebsd-ports@freebsd.org/msg27486.html
>
> --
> Florent Thoumie
> f...@freebsd.org
> FreeBSD Committer
>

Yes, for pkg_install I think I will talk to bapt because he's working
on pkgng so maybe he has a great idea and a better knowledge in C, for
the moment I made some changes in ports/Mk directory but not finished.
I still need to know if a multiple ports could use a same user that
has been added by one of them.

I don't find any good example for this issue.

-- 
Demelier David
___
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: openoffice.org-3 does not build anymore

[David DEMELIER]

2010/10/3 David DEMELIER :
> 2010/10/3 ajtiM :
>> On Sunday 03 October 2010 05:40:33 David DEMELIER wrote:
>>> Hi,
>>>
>>> I can't build openoffice.org-3 anymore,
>>>
>>>         readlicense_oo
>>> need(s) to be rebuilt
>>>
>>> Reason(s):
>>>
>>> ERROR: error 65280 occurred while making
>>> /usr/obj/usr/ports/editors/openoffice.o
>>> rg-3/work/OOO320_m19/readlicense_oo/
>>>
>>> Attention: if you build and deliver the above module(s) you may prolongue
>>> your t he build issuing command "build --from readlicense_oo"
>>>
>>> rmdir /tmp/aTcGY4w2lp
>>> *** Error code 1
>>>
>>> Stop in /usr/ports/editors/openoffice.org-3.
>>>
>>> Cheers,
>>
>> I didn't have problem with RC-3 and it works very good (started yesterday
>> about eight in the evening and it is done).
>>
>> Mitja
>> 
>> http://starikarp.redbubble.com
>>
>
> So I don't understand.
>
> --
> Demelier David
>

It's my fault, I added LOCALIZED_LANG= fr_FR instead of fr-FR. Sorry
for the noise !

-- 
Demelier David
___
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: openoffice.org-3 does not build anymore

[David DEMELIER]

2010/10/12 David DEMELIER :
> 2010/10/3 David DEMELIER :
>> 2010/10/3 ajtiM :
>>> On Sunday 03 October 2010 05:40:33 David DEMELIER wrote:
>>>> Hi,
>>>>
>>>> I can't build openoffice.org-3 anymore,
>>>>
>>>>         readlicense_oo
>>>> need(s) to be rebuilt
>>>>
>>>> Reason(s):
>>>>
>>>> ERROR: error 65280 occurred while making
>>>> /usr/obj/usr/ports/editors/openoffice.o
>>>> rg-3/work/OOO320_m19/readlicense_oo/
>>>>
>>>> Attention: if you build and deliver the above module(s) you may prolongue
>>>> your t he build issuing command "build --from readlicense_oo"
>>>>
>>>> rmdir /tmp/aTcGY4w2lp
>>>> *** Error code 1
>>>>
>>>> Stop in /usr/ports/editors/openoffice.org-3.
>>>>
>>>> Cheers,
>>>
>>> I didn't have problem with RC-3 and it works very good (started yesterday
>>> about eight in the evening and it is done).
>>>
>>> Mitja
>>> 
>>> http://starikarp.redbubble.com
>>>
>>
>> So I don't understand.
>>
>> --
>> Demelier David
>>
>
> It's my fault, I added LOCALIZED_LANG= fr_FR instead of fr-FR. Sorry
> for the noise !
>
> --
> Demelier David
>

When building OOo my Xorg had frozen, the system not because I
successfully shutdown it. Is this a shared memory issue?

-- 
Demelier David
___
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"

portmaster ----clean-package option mistake

[David DEMELIER]

Hello Doug,

I think there is a little completion problem in the zsh completion
file, take a look :

mark...@abricot ~ $ portmaster --


   08:29
option
clean-packages  -- offer to delete stale packages
clean-packages-all  -- delete stale packages without prompting
--always-fetch  -- fetch package even if it already exists locally
--check-depends -- cross-check and update dependency
information for all ports
--check-port-dbdir  -- check for stale entries in /var/db/ports

Reading the man, and typing the clean-packages I assume this
options does not exist. Here is a patch to correct this.

Kind regards,

-- 
Demelier David


zsh-_portmaser.diff
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"

java/openjdk6 now use free openjdk bootstrap packages

[David DEMELIER]

Hello folks,

As I said here 
http://lists.freebsd.org/pipermail/freebsd-ports/2010-September/063813.html

I wanted to do a full-free java/openjdk6 port, now it can builds
itself without installing any
diablo-jdk/sun-jdk/whatever-non-free-jdk.

The PR is located here : http://www.freebsd.org/cgi/query-pr.cgi?pr=151923

Please try on FreeBSD 7 i386, amd64 and tell me if everything is okay.

Kind regards,

-- 
Demelier David
___
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: portmaster ----clean-package option mistake

[David DEMELIER]

2010/11/3 Doug Barton :
> On 11/3/2010 12:27 AM, David DEMELIER wrote:
>>
>> Hello Doug,
>>
>> I think there is a little completion problem in the zsh completion
>> file, take a look :
>>
>> mark...@abricot ~ $ portmaster --
>>
>>
>>        08:29
>> option
>> clean-packages      -- offer to delete stale packages
>> clean-packages-all  -- delete stale packages without prompting
>> --always-fetch          -- fetch package even if it already exists locally
>> --check-depends         -- cross-check and update dependency
>> information for all ports
>> --check-port-dbdir      -- check for stale entries in /var/db/ports
>>
>> Reading the man, and typing the clean-packages I assume this
>> options does not exist. Here is a patch to correct this.
>
> Well that's a bit embarrassing, thanks!  I don't use zsh, so I rely on
> members of the community to help with that. Have you examined the rest of
> the file for any other silly mistakes? I would deeply appreciate it...
>

Everything looks right :-)

-- 
Demelier David
___
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"

devel/git new update des not fetch

[David Demelier]

Hello,

Since my new update of ports tree :

===>  Vulnerability check disabled, database not found
===>  License check disabled, port has not defined LICENSE
===>  Found saved configuration for git-1.7.4.3
=> git-1.7.6.1.tar.bz2 doesn't seem to exist in /usr/ports/distfiles//.
=> Attempting to fetch 
http://kernel.org/pub/software/scm/git/git-1.7.6.1.tar.bz2
fetch: http://kernel.org/pub/software/scm/git/git-1.7.6.1.tar.bz2: 
Service Unavailable
=> Attempting to fetch 
http://www.us.kernel.org/pub/software/scm/git/git-1.7.6.1.tar.bz2
fetch: 
http://www.us.kernel.org/pub/software/scm/git/git-1.7.6.1.tar.bz2: No 
address record
=> Attempting to fetch 
http://www.no.kernel.org/pub/software/scm/git/git-1.7.6.1.tar.bz2
fetch: 
http://www.no.kernel.org/pub/software/scm/git/git-1.7.6.1.tar.bz2: No 
address record
=> Attempting to fetch 
http://www.de.kernel.org/pub/software/scm/git/git-1.7.6.1.tar.bz2
fetch: 
http://www.de.kernel.org/pub/software/scm/git/git-1.7.6.1.tar.bz2: No 
address record
=> Attempting to fetch 
http://www.it.kernel.org/pub/software/scm/git/git-1.7.6.1.tar.bz2
fetch: 
http://www.it.kernel.org/pub/software/scm/git/git-1.7.6.1.tar.bz2: No 
address record
=> Attempting to fetch 
http://www.ru.kernel.org/pub/software/scm/git/git-1.7.6.1.tar.bz2
fetch: 
http://www.ru.kernel.org/pub/software/scm/git/git-1.7.6.1.tar.bz2: No 
address record
=> Attempting to fetch 
http://www.au.kernel.org/pub/software/scm/git/git-1.7.6.1.tar.bz2
fetch: 
http://www.au.kernel.org/pub/software/scm/git/git-1.7.6.1.tar.bz2: No 
address record
=> Attempting to fetch 
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/git-1.7.6.1.tar.bz2
fetch: 
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/git-1.7.6.1.tar.bz2: 
File unavailable (e.g., file not found, no access)

=> Couldn't fetch it - please try to retrieve this
=> port manually into /usr/ports/distfiles// and try again.
*** Error code 1

Cheers,

--
David Demelier
___
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"

Problem with package-recursive target

[David Demelier]

Hello,

Even when I have a clean ports tree (I mean no work under any port) make 
package-recursive always make some garbage like this :


rmdir: /usr/ports/textproc/raptor/work: Directory not empty
*** Error code 1 (ignored)
rmdir: /usr/ports/textproc/rasqal/work: Directory not empty
*** Error code 1 (ignored)
[... snipped for a lot of ports ...]

That does not appears all the time but in my case it appeared when doing 
make package-recursive in www/firefox and editors/libreoffice. It is a 
little bit annoying.


Do you have any clue?

Cheers,


--
David Demelier
___
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"

flashplugin does not work anymore

[David Demelier]

Hello,

My flash plugin has been broken a few days ago, now each time I try to 
access a flash content I can see the following output:


(npviewer.bin:2177): Gtk-WARNING **: cannot open display: :0
*** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC 
client connection

NOTE: child process received `Goodbye', closing down

I use the latest linux-f10-flashplugin-10.3r183.10 version.

Do you have any idea?

Cheers,

--
David Demelier
___
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: flashplugin does not work anymore

[David Demelier]

On 17/10/2011 12:25, Luchesar V. ILIEV wrote:

On 17/10/2011 13:10, David Demelier wrote:

Hello,

My flash plugin has been broken a few days ago, now each time I try to
access a flash content I can see the following output:

(npviewer.bin:2177): Gtk-WARNING **: cannot open display: :0
*** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC
client connection
NOTE: child process received `Goodbye', closing down

I use the latest linux-f10-flashplugin-10.3r183.10 version.

Do you have any idea?

Cheers,



It looks exactly like the problem introduced with the last patch to the
base system...

http://security.freebsd.org/advisories/FreeBSD-SA-11:05.unix.asc

"The patch provided with the initial version of this advisory exposed
the pre-existing bug in FreeBSD's linux emulation code, resulting in
attempts to use UNIX sockets from linux applications failing.  The most
common instance where UNIX sockets were used by linux applications is
in the context of the X windowing system, including the widely used
linux "flash" web browser plugin."

So, perform whatever type of updating you typically use to apply the
fixed patch.

HTH,
Luchesar



I have updated my RELENG_8 src/ and rebuild my kernel but it does not 
change anything.


Cheers,


--
David Demelier
___
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: flashplugin does not work anymore

[David Demelier]

On 17/10/2011 12:25, Luchesar V. ILIEV wrote:

On 17/10/2011 13:10, David Demelier wrote:

Hello,

My flash plugin has been broken a few days ago, now each time I try to
access a flash content I can see the following output:

(npviewer.bin:2177): Gtk-WARNING **: cannot open display: :0
*** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC
client connection
NOTE: child process received `Goodbye', closing down

I use the latest linux-f10-flashplugin-10.3r183.10 version.

Do you have any idea?

Cheers,



It looks exactly like the problem introduced with the last patch to the
base system...

http://security.freebsd.org/advisories/FreeBSD-SA-11:05.unix.asc

"The patch provided with the initial version of this advisory exposed
the pre-existing bug in FreeBSD's linux emulation code, resulting in
attempts to use UNIX sockets from linux applications failing.  The most
common instance where UNIX sockets were used by linux applications is
in the context of the X windowing system, including the widely used
linux "flash" web browser plugin."

So, perform whatever type of updating you typically use to apply the
fixed patch.

HTH,
Luchesar



Forget my last message, I restarted firefox and it works. Thanks

--
David Demelier
___
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"

devel/valgrind fails to build on 9.0

[David Demelier]

Hi there,

Since my update to 9.0 I tried to update valgrind but it fails to build:

cc -B/usr/lib32 -m32 -O2 -g -Wall -Wmissing-prototypes -Wshadow
-Wpointer-arith -Wstrict-prototypes -Wmissing-declarations
-Wno-format-zero-length -fno-strict-aliasing -fpic -O -g
-fno-omit-frame-pointer -fno-strict-aliasing -Wno-long-long -O2 -pipe
-fno-strict-aliasing -Wno-pointer-sign -fno-stack-protector
-nodefaultlibs -shared -Wl,-z,interpose,-z,initfirst -B/usr/lib32 -m32
 -o vgpreload_core-x86-freebsd.so
vgpreload_core_x86_freebsd_so-vg_preloaded.o
/usr/bin/ld: i386:x86-64 architecture of input file `/usr/lib/crti.o'
is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file
`/usr/lib/crtbeginS.o' is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file
`/usr/lib/crtendS.o' is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file `/usr/lib/crtn.o'
is incompatible with i386 output
cc: Internal error: Segmentation fault: 11 (program ld)
Please submit a full bug report.
See http://gcc.gnu.org/bugs.html> for instructions.
gmake[3]: *** [vgpreload_core-x86-freebsd.so] Error 1
gmake[3]: Leaving directory
`/usr/ports/devel/valgrind/work/valgrind-freebsd-3.6.1-2/coregrind'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory
`/usr/ports/devel/valgrind/work/valgrind-freebsd-3.6.1-2/coregrind'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory
`/usr/ports/devel/valgrind/work/valgrind-freebsd-3.6.1-2'
gmake: *** [all] Error 2
*** Error code 1

I'm guessing if my WITHOUT_LIB32 may cause this error. This is on my
amd64 machine.

Cheers,

-- 
Demelier David
___
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: devel/valgrind fails to build on 9.0

[David Demelier]

On 13/01/2012 18:50, David Demelier wrote:

Hi there,

Since my update to 9.0 I tried to update valgrind but it fails to build:

cc -B/usr/lib32 -m32 -O2 -g -Wall -Wmissing-prototypes -Wshadow
-Wpointer-arith -Wstrict-prototypes -Wmissing-declarations
-Wno-format-zero-length -fno-strict-aliasing -fpic -O -g
-fno-omit-frame-pointer -fno-strict-aliasing -Wno-long-long -O2 -pipe
-fno-strict-aliasing -Wno-pointer-sign -fno-stack-protector
-nodefaultlibs -shared -Wl,-z,interpose,-z,initfirst -B/usr/lib32 -m32
  -o vgpreload_core-x86-freebsd.so
vgpreload_core_x86_freebsd_so-vg_preloaded.o
/usr/bin/ld: i386:x86-64 architecture of input file `/usr/lib/crti.o'
is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file
`/usr/lib/crtbeginS.o' is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file
`/usr/lib/crtendS.o' is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file `/usr/lib/crtn.o'
is incompatible with i386 output
cc: Internal error: Segmentation fault: 11 (program ld)
Please submit a full bug report.
Seehttp://gcc.gnu.org/bugs.html>  for instructions.
gmake[3]: *** [vgpreload_core-x86-freebsd.so] Error 1
gmake[3]: Leaving directory
`/usr/ports/devel/valgrind/work/valgrind-freebsd-3.6.1-2/coregrind'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory
`/usr/ports/devel/valgrind/work/valgrind-freebsd-3.6.1-2/coregrind'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory
`/usr/ports/devel/valgrind/work/valgrind-freebsd-3.6.1-2'
gmake: *** [all] Error 2
*** Error code 1

I'm guessing if my WITHOUT_LIB32 may cause this error. This is on my
amd64 machine.

Cheers,



Forget, I didn't have enough swap space...

--
David Demelier
___
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"

Update of devel/glade3 and removal of devel/glade2

[David Demelier]

Hello,

I'm writing the update of glade port. Gnome provides two version, 3.8.1 
for GTK+-2.0 series and 3.10.2 for GTK+-3.0.


Because the both version starts with 3.x.x as version number we should 
create a new port for the GTK+-3.0.


Should I propose something like that ?

devel/glade2 -> removal (old, unused anymore)
devel/glade3 -> rename to devel/glade-gtk2
devel/glade-gtk3 -> new port that I'll write for GTK+-3.0 soon

Cheers,

--
David Demelier
___
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"

Please set a real message for 20120220 in UPDATING

[David Demelier]

Hello,

[quote]

  libungif is obsolete, please deinstall it and rebuild all ports using
  it with graphics/giflib.

[/quote]

This is not easy for people who don't know how to reinstall a port with 
a new origin, and more difficult when a shared library bump in the same 
time, please append something like that:


# portmaster -o graphics/giflib graphics/libungif
# portmaster -r giflib

or

# portupgrade -o graphics/giflib graphics/libungif
# portupgrade -rf giflib

Thanks :)

Cheers,

--
David Demelier
___
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: x11/slim env data gets lost

[David Demelier]

On 26/03/2012 18:24, Steve Frowly wrote:

Hi

I started using x11/slim a week ago and I must say I love it. One thing I 
noticed is that some environment variables don't get set which I normally have 
when I login at the console. To analyze the problem I run:

# logging in via syscons

$ env | sort>  normal-login

# logging in via slim and then invoking an xterm
$ env | sort>  slim-login

A diff showed the following difference:

-PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/home/stvy/bin:/home/stvy/bin:/home/stvy/bin
+PATH=/bin:/usr/bin:/usr/local/bin:/home/stvy/bin

-SHLVL=2
+SHLVL=1

-XTERM_LOCALE=en_US.UTF-8
+XTERM_LOCALE=C


-FTP_PASSIVE_MODE=YES

Does anyone have an idea what's going wrong? I noticed that FTP_PASSIVE_MODE 
gets set in /etc/login.conf.

It's as if slim does not load /etc/login.conf

Thanks you for your help.

--

Steve

___
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"


The login via the tty is done using a full login, the problem with slim 
is that it only calls a shell to run a .xinitrc (or .xsession) located 
in the user home directory thus removing every environment variable.


Because I never found a solution, I removed slim :(

Cheers,

--
David Demelier
___
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"

mercurial broken

[David DEMELIER]

Hello

after an upgrade to 1.7.1, I can't use mercurial anymore :

mark...@melon ~/devel/dotfiles $ hg pull
abort: No module named thread!
Exception AttributeError: "'httpsrepository' object has no attribute
'urlopener'" in > ignored

what is happening ?

Kind regards,

-- 
Demelier David
___
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: mercurial broken

[David DEMELIER]

2010/11/24 Christer Solskogen :
> On Wed, Nov 24, 2010 at 9:30 PM, David DEMELIER
>  wrote:
>> Hello
>>
>> after an upgrade to 1.7.1, I can't use mercurial anymore :
>>
>> mark...@melon ~/devel/dotfiles $ hg pull
>> abort: No module named thread!
>> Exception AttributeError: "'httpsrepository' object has no attribute
>> 'urlopener'" in > > ignored
>>
>> what is happening ?
>>
>
> Dont know about you, but it works fine here:
> $ hg --version
> Mercurial Distributed SCM (version 1.7.1)
> (see http://mercurial.selenic.com for more information)
>
> Copyright (C) 2005-2010 Matt Mackall and others
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> $ uname -a
> FreeBSD shine 8.1-RELEASE-p1 FreeBSD 8.1-RELEASE-p1 #0: Sat Nov 13
> 13:09:55 CET 2010     r...@shine:/usr/obj/usr/src/sys/SHINE  amd64
>
> I also tried cloning from https (and pulling) - No error.
>
> --
> chs,
>

Yes it seems to be python, the port was missing THREADS options.

Sorry for the noise.

Cheers,

-- 
Demelier David
___
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"

Broken x11-themes/icons-tango ?

[David DEMELIER]

Hello,

I was surprised to see black squares around tango icons, I checked the
tango icons and they looks okay. It must be a problem deeper. Perhaps
in gtk or in library handling png/svg files ?

Take a look at this picture : http://files.malikania.fr/tango-bug.png

It's generated on two machines with :

$ cat ~/.gtkrc-2.0
gtk-theme-name = "Clearlooks"
gtk-font-name = "Dejavu Sans 8"
gtk-icon-theme-name = "Tango"

Kind regards,

-- 
Demelier David
___
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"

Proposal moving *spell dicts to ports/textproc/*spell/dicts

[David DEMELIER]

Hi,

As I said some weeks ago I personally don't like much the use of
ports/{french,chinese,whatever}/ directories. I saw that openbsd
created sub directories in the aspell port. I think this is a really
good idea, it's really easier to find.

I don't think german/ispell french/aspell textproc/gu-aspell are
really easy to find.

I propose creating a ports/textproc/aspell/dicts and same for
textproc/ispell and textproc/hunspell and moving every spellings ports
to these directories.

-- 
Demelier David
___
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: Proposal moving *spell dicts to ports/textproc/*spell/dicts

[David DEMELIER]

2010/12/4 Thierry Thomas :
> Le sam  4 déc 10 à 11:58:44 +0100, David DEMELIER 
>  écrivait :
>> Hi,
>
> Hello,
>
>> As I said some weeks ago I personally don't like much the use of
>> ports/{french,chinese,whatever}/ directories. I saw that openbsd
>> created sub directories in the aspell port. I think this is a really
>> good idea, it's really easier to find.
>>
>> I don't think german/ispell french/aspell textproc/gu-aspell are
>> really easy to find.
>>
>> I propose creating a ports/textproc/aspell/dicts and same for
>> textproc/ispell and textproc/hunspell and moving every spellings ports
>> to these directories.
>
> I don't know about hunspell and ispell, but aspell's dictionaries are
> maintained and updated independently, at different dates: its why these
> are separate ports.
>
> Regards,
> --
> Th. Thomas.
>

Yes but I don't want to make one big dict/ port. I would like to move
all aspell languages ports into aspell/dicts/ and then you go under
ports/textproc/aspell/dicts/fr && make install for example :)

Cheers,

-- 
Demelier David
___
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"

mupen64plus segfaults

[David DEMELIER]

Hi,

After an update, I have removed ~/.mupen64plus and
~/.config/mupen64plus but it segfaults when starting :

mark...@melon ~ $ mupen64plus documents/roms/N64/Mario\ Kart\ 64\
\(U\)\ \[\!\].z64
 __  __ __   _  _     _
|  \/  |_   _ _ __   ___ _ __  / /_ | || | |  _ \| |_   _ ___
| |\/| | | | | '_ \ / _ \ '_ \| '_ \| || |_| |_) | | | | / __|
| |  | | |_| | |_) |  __/ | | | (_) |__   _|  __/| | |_| \__ \
|_|  |_|\__,_| .__/ \___|_| |_|\___/   |_| |_|   |_|\__,_|___/
 |_| http://code.google.com/p/mupen64plus/
Mupen64Plus Console User-Interface Version 1.99.4

UI-console: attached to core library 'Mupen64Plus Core' version 1.99.4
Includes support for Dynamic Recompiler.
Core Warning: Couldn't open configuration file
'/home/markand/.config/mupen64plus/mupen64plus.cfg'.  Using defaults.
Core: Goodname: Mario Kart 64 (U) [!]
Core: Name: MARIOKART64
Core: MD5: 3A67D9986F54EB282924FCA4CD5F6DFF
Core: CRC: b655503e 52da922e
Core: Imagetype: .z64 (native)
Core: Rom size: 12582912 bytes (or 12 Mb or 96 Megabits)
Core: Version: 4614
Core: Manufacturer: 4e00
Core: Country: USA
UI-Console: Cheat codes disabled.
UI-console: using Video plugin: 
UI-console: using Audio plugin: 
UI-console: using Input plugin: 
UI-console: using RSP plugin: 
Core Warning: No video plugin attached.  There will be no video output.
Core Warning: No audio plugin attached.  There will be no sound output.
Core Warning: No input plugin attached.  You won't be able to control the game.
zsh: segmentation fault  mupen64plus documents/roms/N64/Mario\ Kart\
64\ \(U\)\ \[!\].z64

I wonder why it does not attach any i/o output.

-- 
Demelier David
___
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: mupen64plus segfaults

[David DEMELIER]

2010/12/13 David DEMELIER :
> Hi,
>
> After an update, I have removed ~/.mupen64plus and
> ~/.config/mupen64plus but it segfaults when starting :
>
> mark...@melon ~ $ mupen64plus documents/roms/N64/Mario\ Kart\ 64\
> \(U\)\ \[\!\].z64
>  __  __                         __   _  _     _
> |  \/  |_   _ _ __   ___ _ __  / /_ | || | |  _ \| |_   _ ___
> | |\/| | | | | '_ \ / _ \ '_ \| '_ \| || |_| |_) | | | | / __|
> | |  | | |_| | |_) |  __/ | | | (_) |__   _|  __/| | |_| \__ \
> |_|  |_|\__,_| .__/ \___|_| |_|\___/   |_| |_|   |_|\__,_|___/
>             |_|         http://code.google.com/p/mupen64plus/
> Mupen64Plus Console User-Interface Version 1.99.4
>
> UI-console: attached to core library 'Mupen64Plus Core' version 1.99.4
>            Includes support for Dynamic Recompiler.
> Core Warning: Couldn't open configuration file
> '/home/markand/.config/mupen64plus/mupen64plus.cfg'.  Using defaults.
> Core: Goodname: Mario Kart 64 (U) [!]
> Core: Name: MARIOKART64
> Core: MD5: 3A67D9986F54EB282924FCA4CD5F6DFF
> Core: CRC: b655503e 52da922e
> Core: Imagetype: .z64 (native)
> Core: Rom size: 12582912 bytes (or 12 Mb or 96 Megabits)
> Core: Version: 4614
> Core: Manufacturer: 4e00
> Core: Country: USA
> UI-Console: Cheat codes disabled.
> UI-console: using Video plugin: 
> UI-console: using Audio plugin: 
> UI-console: using Input plugin: 
> UI-console: using RSP plugin: 
> Core Warning: No video plugin attached.  There will be no video output.
> Core Warning: No audio plugin attached.  There will be no sound output.
> Core Warning: No input plugin attached.  You won't be able to control the 
> game.
> zsh: segmentation fault  mupen64plus documents/roms/N64/Mario\ Kart\
> 64\ \(U\)\ \[!\].z64
>
> I wonder why it does not attach any i/o output.
>
> --
> Demelier David
>

Well, I see the problem :

mupen64plus --plugindir /usr/local/lib

seems to solve the problem since the mupen64plus plugins are in
/usr/local/lib/ instead of /usr/local/lib/mupen64plus/.

-- 
Demelier David
___
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: mupen64plus segfaults

[David Demelier]

i does not build on i386 8.1-RELEASE neither.

===>  Patching for mupen64plus-video-rice-1.99.4
===>   Converting DOS text file to UNIX text file:
===>   mupen64plus-video-rice-1.99.4 depends on executable: gmake - found
===>   mupen64plus-video-rice-1.99.4 depends on file: 
/usr/local/bin/sdl-config - found
===>   mupen64plus-video-rice-1.99.4 depends on shared library: GLU.1 - 
found

===>  Configuring for mupen64plus-video-rice-1.99.4
===>  Building for mupen64plus-video-rice-1.99.4
CC  _obj/liblinux/BMGImage.o
CC  _obj/liblinux/bmp.o
CC  _obj/liblinux/pngrw.o
CC  _obj/osal_dynamiclib_unix.o
CC  _obj/osal_files_unix.o
CC  _obj/liblinux/BMGUtils.o
CXX _obj/Blender.o
CXX _obj/Combiner.o
CXX _obj/CombinerTable.o
CXX _obj/Config.o
CXX _obj/ConvertImage.o
CXX _obj/ConvertImage16.o
CXX _obj/CNvTNTCombiner.o
CXX _obj/Debugger.o
CXX _obj/DecodedMux.o
CXX _obj/DirectXDecodedMux.o
CXX _obj/DeviceBuilder.o
CXX _obj/FrameBuffer.o
CXX _obj/GeneralCombiner.o
CXX _obj/GraphicsContext.o
CXX _obj/OGLCombiner.o
CXX _obj/OGLCombinerNV.o
CXX _obj/OGLCombinerTNT2.o
CXX _obj/OGLDecodedMux.o
CXX _obj/OGLExtCombiner.o
CXX _obj/OGLExtensions.o
CXX _obj/OGLExtRender.o
CXX _obj/OGLFragmentShaders.o
CXX _obj/OGLGraphicsContext.o
CXX _obj/OGLRender.o
CXX _obj/OGLRenderExt.o
CXX _obj/OGLTexture.o
CXX _obj/Render.o
CXX _obj/RenderBase.o
../../src/RenderBase.cpp: In function 'void SSEVec3Transform(int)':
../../src/RenderBase.cpp:478: error: unknown register name '%xmm7' in 'asm'
../../src/RenderBase.cpp:478: error: unknown register name '%xmm6' in 'asm'
../../src/RenderBase.cpp:478: error: unknown register name '%xmm5' in 'asm'
../../src/RenderBase.cpp:478: error: unknown register name '%xmm4' in 'asm'
../../src/RenderBase.cpp:478: error: unknown register name '%xmm1' in 'asm'
../../src/RenderBase.cpp:478: error: unknown register name '%xmm0' in 'asm'
../../src/RenderBase.cpp: In function 'void SSEVec3TransformNormal()':
../../src/RenderBase.cpp:617: error: unknown register name '%xmm7' in 'asm'
../../src/RenderBase.cpp:617: error: unknown register name '%xmm6' in 'asm'
../../src/RenderBase.cpp:617: error: unknown register name '%xmm5' in 'asm'
../../src/RenderBase.cpp:617: error: unknown register name '%xmm4' in 'asm'
../../src/RenderBase.cpp:617: error: unknown register name '%xmm1' in 'asm'
../../src/RenderBase.cpp:617: error: unknown register name '%xmm0' in 'asm'
../../src/RenderBase.cpp: In function 'unsigned int SSELightVert()':
../../src/RenderBase.cpp:1266: error: unknown register name '%xmm5' in 'asm'
../../src/RenderBase.cpp:1266: error: unknown register name '%xmm4' in 'asm'
../../src/RenderBase.cpp:1266: error: unknown register name '%xmm3' in 'asm'
../../src/RenderBase.cpp:1266: error: unknown register name '%xmm1' in 'asm'
../../src/RenderBase.cpp:1266: error: unknown register name '%xmm0' in 'asm'
gmake: *** [_obj/RenderBase.o] Error 1
*** Error code 1

Stop in /usr/ports/emulators/mupen64plus-video-rice.
*** Error code 1

Stop in /usr/ports/emulators/mupen64plus-video-rice.
*** Error code 1

Stop in /usr/ports/emulators/mupen64plus.

Did you try before commit? :-)

Cheers
___
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"

emulators/visualboyadvance-m fails to build

[David Demelier]

Hello,

Today I wanted to compile visualboyadvance-m on my amd64 8.2-PRERELEASE:

mark...@melon ...ators/visualboyadvance-m $ sudo make
===>  Vulnerability check disabled, database not found
===>  License check disabled, port has not defined LICENSE
===>  Found saved configuration for visualboyadvance-m-1.8.0r945_1
===>  Extracting for visualboyadvance-m-1.8.0r945_1
=> SHA256 Checksum OK for visualboyadvance-m-1.8.0r945.tar.bz2.
===>  Patching for visualboyadvance-m-1.8.0r945_1
===>   Converting DOS text files to UNIX text files
===>  Applying FreeBSD patches for visualboyadvance-m-1.8.0r945_1
===>   visualboyadvance-m-1.8.0r945_1 depends on file: 
/usr/local/lib/libsfml-system.so - found
===>   visualboyadvance-m-1.8.0r945_1 depends on file: 
/usr/local/libdata/pkgconfig/x11.pc - found
===>   visualboyadvance-m-1.8.0r945_1 depends on file: 
/usr/local/libdata/pkgconfig/xext.pc - found
===>   visualboyadvance-m-1.8.0r945_1 depends on file: 
/usr/local/bin/sdl-config - found
===>   visualboyadvance-m-1.8.0r945_1 depends on file: 
/usr/local/bin/intltool-extract - found
===>   visualboyadvance-m-1.8.0r945_1 depends on executable: pkg-config 
- found
===>   visualboyadvance-m-1.8.0r945_1 depends on file: 
/usr/local/bin/cmake - found
===>   visualboyadvance-m-1.8.0r945_1 depends on shared library: png.6 - 
found
===>   visualboyadvance-m-1.8.0r945_1 depends on shared library: 
cairomm-1.0.1 - found
===>   visualboyadvance-m-1.8.0r945_1 depends on shared library: 
gtkmm-2.4 - found
===>   visualboyadvance-m-1.8.0r945_1 depends on shared library: 
glibmm-2.4 - found
===>   visualboyadvance-m-1.8.0r945_1 depends on shared library: 
giomm-2.4 - found
===>   visualboyadvance-m-1.8.0r945_1 depends on shared library: 
glademm-2.4 - found
===>   visualboyadvance-m-1.8.0r945_1 depends on shared library: 
gdkglextmm-x11-1.2 - found
===>   visualboyadvance-m-1.8.0r945_1 depends on shared library: GL.1 - 
found
===>   visualboyadvance-m-1.8.0r945_1 depends on shared library: GLU.1 - 
found
===>   visualboyadvance-m-1.8.0r945_1 depends on shared library: 
SDL-1.2.11 - found
===>   visualboyadvance-m-1.8.0r945_1 depends on shared library: 
atk-1.0.0 - found
===>   visualboyadvance-m-1.8.0r945_1 depends on shared library: 
glib-2.0.0 - found
===>   visualboyadvance-m-1.8.0r945_1 depends on shared library: 
gtk-x11-2.0.0 - found
===>   visualboyadvance-m-1.8.0r945_1 depends on shared library: 
pango-1.0.0 - found

===>  Configuring for visualboyadvance-m-1.8.0r945_1
/bin/mkdir -p 
/usr/obj/usr/ports/emulators/visualboyadvance-m/work/visualboyadvance-m-1.8.0r945
CMake Error at 
/usr/local/share/cmake/Modules/CMakeDetermineASMCompiler.cmake:68 
(CMAKE_DETERMINE_COMPILER_ID_VENDOR):

  Unknown CMake command "CMAKE_DETERMINE_COMPILER_ID_VENDOR".
Call Stack (most recent call first):
  CMakeLists.txt:2 (PROJECT)


CMake Error: Error required internal CMake variable not set, cmake may 
be not be built correctly.

Missing variable is:
CMAKE_ASM_COMPILER_ENV_VAR
CMake Error: Could not find cmake module 
file:/usr/obj/usr/ports/emulators/visualboyadvance-m/work/visualboyadvance-m-1.8.0r945/CMakeFiles/CMakeASMCompiler.cmake
CMake Error: Error required internal CMake variable not set, cmake may 
be not be built correctly.

Missing variable is:
CMAKE_C_COMPILER_ENV_VAR
CMake Error: Could not find cmake module 
file:/usr/obj/usr/ports/emulators/visualboyadvance-m/work/visualboyadvance-m-1.8.0r945/CMakeFiles/CMakeCCompiler.cmake
CMake Error: Error required internal CMake variable not set, cmake may 
be not be built correctly.

Missing variable is:
CMAKE_CXX_COMPILER_ENV_VAR
CMake Error: Could not find cmake module 
file:/usr/obj/usr/ports/emulators/visualboyadvance-m/work/visualboyadvance-m-1.8.0r945/CMakeFiles/CMakeCXXCompiler.cmake

-- Configuring incomplete, errors occurred!
You have changed variables that require your cache to be deleted.
Configure will be re-run and you may have to reset some variables.
The following variables have changed:
CMAKE_C_COMPILER= cc
CMAKE_CXX_COMPILER= c++

-- Generating done
-- Build files have been written to: 
/usr/obj/usr/ports/emulators/visualboyadvance-m/work/visualboyadvance-m-1.8.0r945

*** Error code 1

Stop in /usr/ports/emulators/visualboyadvance-m.
*** Error code 1

Stop in /usr/ports/emulators/visualboyadvance-m.

Kind regards,
___
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"

libksba update broken

[David Demelier]

Hello,

gnupg and libksba are not installed :

===>Verifying install for ksba.17 in /usr/ports/security/libksba
===>   Returning to build of gnupg-2.0.16_3
Error: shared library "ksba.17" does not exist
*** Error code 1

Stop in /usr/ports/security/gnupg.
*** Error code 1

Stop in /usr/ports/security/gnupg.

Cheersm
___
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: libksba update broken

[David Demelier]

On 16/12/2010 16:30, David Demelier wrote:

Hello,

gnupg and libksba are not installed :

===> Verifying install for ksba.17 in /usr/ports/security/libksba
===> Returning to build of gnupg-2.0.16_3
Error: shared library "ksba.17" does not exist
*** Error code 1

Stop in /usr/ports/security/gnupg.
*** Error code 1

Stop in /usr/ports/security/gnupg.

Cheers,


Please consider the following patch :

--- Makefile.orig   2010-12-16 16:40:08.0 +0100
+++ Makefile2010-12-16 16:40:16.0 +0100
@@ -21,7 +21,7 @@
 LIB_DEPENDS=   assuan.0:${PORTSDIR}/security/libassuan \
gcrypt.17:${PORTSDIR}/security/libgcrypt \
gpg-error:${PORTSDIR}/security/libgpg-error \
-   ksba.17:${PORTSDIR}/security/libksba \
+   ksba.18:${PORTSDIR}/security/libksba \
pth.20:${PORTSDIR}/devel/pth

 LICENSE=   GPLv3 LGPL3

Also please add an entry in UPDATING to tell user to use portmaster -w 
to keep old libraries while all ports depending on libksba are not updated.


(like gettext)

Cheers,
___
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: libksba update broken

[David Demelier]

On 16/12/2010 16:44, Greg Larkin wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

David Demelier wrote:

Hello,

gnupg and libksba are not installed :

===> Verifying install for ksba.17 in /usr/ports/security/libksba
===>Returning to build of gnupg-2.0.16_3
Error: shared library "ksba.17" does not exist
*** Error code 1

Stop in /usr/ports/security/gnupg.
*** Error code 1

Stop in /usr/ports/security/gnupg.



Hi David,

Please update your ports tree and try it again.  I committed the fix an
hour or so ago, so it's possible that portsnap will take a little while
to create its update package.

Thank you,
Greg
- --
Greg Larkin

http://www.FreeBSD.org/   - The Power To Serve
http://www.sourcehosting.net/ - Ready. Set. Code.
http://twitter.com/sourcehosting/ - Follow me, follow you
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFNCjPN0sRouByUApARAu6cAJ4lSWfw9p7fvVZebnEjBGK0sUHXsQCgrWEm
TN7RB+oeqxXa2WkJpUxYbN4=
=fctV
-END PGP SIGNATURE-



Oh you were faster than me! ignore my patch and thanks for the work :-)

Best regards,

David.
___
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"

portmaster: print /usr/ports/UPDATING on update

[David Demelier]

Hi,

A lot of people always forget to read UPDATING (that's normal we'll are 
humans).


Each entry in UPDATING is like "AFFECTS: users of net-mgmt/flowd" so if 
an update of net-mgmt/flowd is available and a *recent* entry in 
UPDATING talks about then print the message.


This can prevent a lot of breakage and useless noise on lists. What do 
you think ?


Merry Christmas and happy holidays !

David.
___
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"

java/netbeans segfaults

[David Demelier]

Hello,

I just wanted to try netbeans here on FreeBSD :

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00080225dd34, pid=38650, tid=34805431360
#
# JRE version: 6.0-b20
# Java VM: OpenJDK 64-Bit Server VM (17.0-b16 mixed mode bsd-amd64 )
# Problematic frame:
#
[error occurred during error reporting (printing problematic frame), id 0xb]

# An error report file with more information is saved as:
# /home/markand/hs_err_pid38650.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
Abort trap

The file hs_err_pid38650.log is long so I uploaded it right here :

http://files.malikania.fr/hs_err_pid38650.log

Is it possible that openjdk could be the problem?

Cheers,

--
David Demelier
___
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"

ldconfig -r does not show devel/sfml libraries

[David Demelier]

Hello,

I'm writing a patch for emulators/visualboyadvance-m because it needs 
libsfml as LIB_DEPENDS and not only BUILD_DEPENDS.


The problem is that ldconfig -r does not show the libsfml libraries so I 
can't actually add a correct LIB_DEPEND line see :


mark...@melon ...ators/visualboyadvance-m $ ldconfig -r | grep libsfml
mark...@melon ...ators/visualboyadvance-m $

mark...@melon ...ators/visualboyadvance-m $ ls /usr/local/lib/libsfml-*
/usr/local/lib/libsfml-audio.so 
/usr/local/lib/libsfml-graphics.so.1.6 /usr/local/lib/libsfml-system.so 
  /usr/local/lib/libsfml-window.so.1.6
/usr/local/lib/libsfml-audio.so.1.6/usr/local/lib/libsfml-network.so 
 /usr/local/lib/libsfml-system.so.1.6
/usr/local/lib/libsfml-graphics.so 
/usr/local/lib/libsfml-network.so.1.6  /usr/local/lib/libsfml-window.so


the weird thing is that ldconfig -m is ran after the devel/sfml install.

What can I do to fix?

Kind regards,

--
David Demelier
___
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"

qt4 raster graphics rendering is broken

[David Demelier]

Hello,

It seems that the Qt4 raster graphic system is broken under FreeBSD. If 
you have Qt4 installed try :


qtconfig-qt4 -graphicssystem raster

This will result in a “blank” window with some errors :

X Error: BadAccess (attempt to access private resource denied) 10
  Extension:139 (MIT-SHM)
  Minor opcode: 1 (X_ShmAttach)
  Resource id:  0x14d
X Error: BadShmSeg (invalid shared segment parameter) 146
  Extension:139 (MIT-SHM)
  Minor opcode: 3 (X_ShmPutImage)
  Resource id:  0x24a
X Error: BadShmSeg (invalid shared segment parameter) 146
  Extension:139 (MIT-SHM)
  Minor opcode: 3 (X_ShmPutImage)
  Resource id:  0x24a
X Error: BadShmSeg (invalid shared segment parameter) 146
  Extension:139 (MIT-SHM)
  Minor opcode: 3 (X_ShmPutImage)
  Resource id:  0x24a
X Error: BadShmSeg (invalid shared segment parameter) 146
  Extension:139 (MIT-SHM)
  Minor opcode: 2 (X_ShmDetach)
  Resource id:  0x24a

This was reported first, by Tiled.

Cheers,

--
David Demelier
___
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: [PATCH] Proposal for a new option framework

[David Demelier]

On 17/11/2010 15:58, Baptiste Daroussin wrote:

Hi all,

I'd like to expose you a new proposal for the framework option.

First the problem with the actual situation.
the option framework has some problems :
- for a given option we have two variable : WITH_OPT WITHOUT_OPT only
having to check one will be great.
- the option framework isn't consistent : if you set a WITH_BLA in
/etc/make.conf, make config doesn't mind about it for example.

So here is my proposal and a patch that implements it :

for porters :
3 types of options : simple, group and list
- simple options are the same as the current options (ie user can
activate what ever they wants)
- group options are options where at least one has to be set (1-N)
- list options are options where only one has to be set and only one
can be set (exclusive options)

a maintainer can defined them it the ports and some can be defined system wide.

every options can have a description but this is not mandatory.

maintainer can set default options (DEFAULT_OPTS) and remove global
options that the ports doesn't support yet OPTS_RM.

in a ports how to define them like this

OPTS= OPT1 OPT2 OPT3

OPTS_GROUP= GRP1 GRP2
OPTS_GROUP_GRP1= OPT4 OPT5
OPTS_GROUP_GRP2= OPT6 OPT7

OPTS_LIST= LIST1
OPTS_LIST_LIST1= OPT8 OTP9 OPT10


DEFAULT_OPTS= OPT2 OPT3 OPT9 OPT7 OPT8 OPT4
OPTS_RM= NLS NOPORTDOCS

to define a desciption for a given option :
OPT1_DESC= "Description of my option"

make showoptions will present all the options and their descriptions :

===>  The following configuration options are available:
OPT1=off: Description of my option
OPT2=on
OPT3=on
>  Options available for the group GRP1: you have to choose at
least one of them
OPT4=on
OPT5=off
>  Options available for the group GRP2: you have to choose at
least one of them
OPT6=off
OPT7=on
>  Options available for the group LIST1: you have to select only one of 
them
OPT8=on
OPT9=off
OPT10=off

a user can set in make.conf global options for the whole ports :
OPTS_SET= OPT1 OPT3
of unset them system wide
OPTS_UNSET= OPT10 OPT15

per port options can be specified in two ways for a given ports :
through /etc/make.conf:
${UNIQUENAME}_OPTS_SET= OPT1

${UNIQUENAME}_OPTS_UNSET= OPT2

for zsh it would be:
zsh_OPTS_SET= OPT1
zsh_OPTS_UNSET= OPT2

through /var/db/ports/${UNIQUENAME}/opts (in case we add a dialog like feature)
OPTS_SET= OPT1
OPTS_UNSET= OPT2

The framework check how the options are set in the following way :
1/ set the default options has wanted by the maintainer
2/ override them using the system wide options (OPTS_(UN)SET)
3/ the per ports defined options in /var/db/ports/${UNIQUENAME}/opts
4/ the per ports defined options in make.conf ${UNIQUENAME}_OPTS_(UN)SET

We can maintain some generic options descriptions like it is done in the KNOBS

for the maintainer to check if an option is set or not, we do not need
to choose between WITHOUT ou WITH option the options as to be checked
that way:
if !empty(PORTS_OPTS:MOPT1)
@${ECHO_CMD} " the options OPT1 is set"
.else
@${ECHO_CMD} "the options OPT2 is not set"
.endif

the framework check (check-options) for the consitency for the options
set (exclusive options and 1-n option)

In the patch nothing is activated by default (user has make
check-options himself currently)
there is nothing to create /var/db/ports/${UNIQUENAME}/opts it don't
really like having a gui for that but I understand some prefers and I
am checking how to make dialog4ports able to do the job.

The new framework can live with the old one
The implementation is really really simple.
In the implementation I added 3 global options: NOPORTDOCS NOPORTDATA
NOPORTEXAMPLES
Variable names are temporary if you have better ideas :)

I think it is quite easy to extend to add features later.

http://people.freebsd.org/~bapt/ports-newopts.patch



This is the best thing that could happens to the FreeBSD ports. Now the 
ports OPTIONS framework lacks a lot of feature. We can't select "only 
one" option in a list of (like pkgsrc does) and this new framework may 
provides this feature !


The group feature may helps in a backend dependency too!

I really like this new framework and hope will be bring to ports before 
2026 :-).


Thanks bapt.

--
David Demelier
___
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: [PATCH] Proposal for a new option framework

[David Demelier]

On 17/11/2010 15:58, Baptiste Daroussin wrote:

Hi all,

I'd like to expose you a new proposal for the framework option.

First the problem with the actual situation.
the option framework has some problems :
- for a given option we have two variable : WITH_OPT WITHOUT_OPT only
having to check one will be great.
- the option framework isn't consistent : if you set a WITH_BLA in
/etc/make.conf, make config doesn't mind about it for example.

So here is my proposal and a patch that implements it :

for porters :
3 types of options : simple, group and list
- simple options are the same as the current options (ie user can
activate what ever they wants)
- group options are options where at least one has to be set (1-N)
- list options are options where only one has to be set and only one
can be set (exclusive options)

a maintainer can defined them it the ports and some can be defined system wide.

every options can have a description but this is not mandatory.

maintainer can set default options (DEFAULT_OPTS) and remove global
options that the ports doesn't support yet OPTS_RM.

in a ports how to define them like this

OPTS= OPT1 OPT2 OPT3

OPTS_GROUP= GRP1 GRP2
OPTS_GROUP_GRP1= OPT4 OPT5
OPTS_GROUP_GRP2= OPT6 OPT7

OPTS_LIST= LIST1
OPTS_LIST_LIST1= OPT8 OTP9 OPT10


DEFAULT_OPTS= OPT2 OPT3 OPT9 OPT7 OPT8 OPT4
OPTS_RM= NLS NOPORTDOCS

to define a desciption for a given option :
OPT1_DESC= "Description of my option"

make showoptions will present all the options and their descriptions :

===>  The following configuration options are available:
OPT1=off: Description of my option
OPT2=on
OPT3=on
>  Options available for the group GRP1: you have to choose at
least one of them
OPT4=on
OPT5=off
>  Options available for the group GRP2: you have to choose at
least one of them
OPT6=off
OPT7=on
>  Options available for the group LIST1: you have to select only one of 
them
OPT8=on
OPT9=off
OPT10=off

a user can set in make.conf global options for the whole ports :
OPTS_SET= OPT1 OPT3
of unset them system wide
OPTS_UNSET= OPT10 OPT15

per port options can be specified in two ways for a given ports :
through /etc/make.conf:
${UNIQUENAME}_OPTS_SET= OPT1

${UNIQUENAME}_OPTS_UNSET= OPT2

for zsh it would be:
zsh_OPTS_SET= OPT1
zsh_OPTS_UNSET= OPT2

through /var/db/ports/${UNIQUENAME}/opts (in case we add a dialog like feature)
OPTS_SET= OPT1
OPTS_UNSET= OPT2

The framework check how the options are set in the following way :
1/ set the default options has wanted by the maintainer
2/ override them using the system wide options (OPTS_(UN)SET)
3/ the per ports defined options in /var/db/ports/${UNIQUENAME}/opts
4/ the per ports defined options in make.conf ${UNIQUENAME}_OPTS_(UN)SET

We can maintain some generic options descriptions like it is done in the KNOBS

for the maintainer to check if an option is set or not, we do not need
to choose between WITHOUT ou WITH option the options as to be checked
that way:
if !empty(PORTS_OPTS:MOPT1)
@${ECHO_CMD} " the options OPT1 is set"
.else
@${ECHO_CMD} "the options OPT2 is not set"
.endif

the framework check (check-options) for the consitency for the options
set (exclusive options and 1-n option)

In the patch nothing is activated by default (user has make
check-options himself currently)
there is nothing to create /var/db/ports/${UNIQUENAME}/opts it don't
really like having a gui for that but I understand some prefers and I
am checking how to make dialog4ports able to do the job.

The new framework can live with the old one
The implementation is really really simple.
In the implementation I added 3 global options: NOPORTDOCS NOPORTDATA
NOPORTEXAMPLES
Variable names are temporary if you have better ideas :)

I think it is quite easy to extend to add features later.

http://people.freebsd.org/~bapt/ports-newopts.patch

regards,
Bapt
___
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"


This is the best thing that could happens to the FreeBSD ports. Now the 
ports OPTIONS framework lacks a lot of feature. We can't select "only 
one" option in a list of (like pkgsrc does) and this new framework may 
provides this feature !


The group feature may helps in a backend dependency too!

I really like this new framework and hope will be bring to ports before 
2026 :-).


Thanks bapt.

--
David Demelier
___
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"

package-recursive target troubles

[David DEMELIER]

Hello,

What's happening to the package-recursive target ? I always has the following :

===>  Building package for lighttpd-1.4.28_4
===>   Generating temporary packing list
===>   Generating temporary packing list
===>   Generating temporary packing list
rmdir: /usr/obj/usr/ports/databases/libmemcache/work: Directory not empty
*** Error code 1 (ignored)
rmdir: /usr/obj/usr/ports/misc/e2fsprogs-libuuid/work: Directory not empty
*** Error code 1 (ignored)
rmdir: /usr/obj/usr/ports/databases/sqlite3/work: Directory not empty
*** Error code 1 (ignored)
rmdir: /usr/obj/usr/ports/devel/gamin/work: Directory not empty
*** Error code 1 (ignored)
===>   Generating temporary packing list
rmdir: /usr/obj/usr/ports/www/spawn-fcgi/work: Directory not empty
*** Error code 1 (ignored)
===>   Generating temporary packing list
rmdir: /usr/obj/usr/ports/archivers/unzip/work: Directory not empty
*** Error code 1 (ignored)
rmdir: /usr/obj/usr/ports/lang/tcl85/work: Directory not empty
*** Error code 1 (ignored)
rmdir: /usr/obj/usr/ports/lang/tcl-modules/work: Directory not empty
*** Error code 1 (ignored)
===>   Generating temporary packing list
rmdir: /usr/obj/usr/ports/devel/glib20/work: Directory not empty
*** Error code 1 (ignored)
===>   Generating temporary packing list
===>   Generating temporary packing list
rmdir: /usr/obj/usr/ports/lang/python26/work: Directory not empty
*** Error code 1 (ignored)

These error code are not dangerous but painful. Am I missing something or not?

Cheers,

-- 
Demelier David
___
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"

Gajim does not starts

[David Demelier]

Hello,

I just realized that gajim does not starts anymore :

markand@Melon ~ $ gajim
** Message: pygobject_register_sinkfunc is deprecated (GstObject)
nslookup: not found

I know this is a very useful message, but I can't help more.

Are you expecting the same behavior ?

Cheers,

--
David Demelier
___
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: Gajim does not starts

[David Demelier]

On 22/02/2011 22:27, David Demelier wrote:

Hello,

I just realized that gajim does not starts anymore :

markand@Melon ~ $ gajim
** Message: pygobject_register_sinkfunc is deprecated (GstObject)
nslookup: not found

I know this is a very useful message, but I can't help more.

Are you expecting the same behavior ?

Cheers,



Sorry it seems that I compiled my world with WITHOUT_BIND.

Cheers,

--
David Demelier
___
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: Gajim does not starts

[David Demelier]

On 22/02/2011 22:35, Doug Barton wrote:

On 02/22/2011 13:30, David Demelier wrote:

On 22/02/2011 22:27, David Demelier wrote:

Hello,

I just realized that gajim does not starts anymore :

markand@Melon ~ $ gajim
** Message: pygobject_register_sinkfunc is deprecated (GstObject)
nslookup: not found

I know this is a very useful message, but I can't help more.

Are you expecting the same behavior ?

Cheers,



Sorry it seems that I compiled my world with WITHOUT_BIND.


It's wacky that this would require nslookup, but if you don't want/need
a complete BIND installation you can take a look at ports/dns/bind-tools.


hth,

Doug




Now gajim starts but quits as soon as it started...

--
David Demelier
___
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"

Find a corrupt port

[David Demelier]

Hello,

It seems I have a corrupted port on my system :

$ pkg_info
[...]
dmxproto-2.3DMX extension headers
pkg_info: corrupted record (pkgdep line without argument), ignoring
pkg_info: corrupted record (pkgdep line without argument), ignoring
pkg_info: corrupted record (pkgdep line without argument), ignoring
pkg_info: corrupted record (pkgdep line without argument), ignoring
docproj-1.17_4  The "meta-port" for the FreeBSD Documentation Project
[...]

Because it happens after dmxproto O tought it was this one, but after a 
make deinstall reinstall in x11/dmxproto the corrupt message is still 
there so I'm guessing if it's the corrupted port.


How can I easily find?

Cheers,

--
David Demelier
___
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"