Re: fprint (finger print sensor framework) port ready for testing
Yupp I even set the permissions 777 and added the user i tested to group operator still no joy ive used the upek port no problems even with GDM. the "root" user works great, but regular users cant even register ls -al /dev/ugen* crw-rw-rw- 1 root operator0, 84 Apr 15 14:14 /dev/ugen0 crw-rw-rw- 1 root operator0, 85 Apr 15 14:14 /dev/ugen0.1 crw-rw-rw- 1 root operator0, 86 Apr 15 14:14 /dev/ugen0.2 crw-rw-rw- 1 root operator0, 87 Apr 15 14:14 /dev/ugen0.3 crw-rw-rw- 1 root operator0, 88 Apr 15 14:14 /dev/ugen0.4 crwxrwxrwx 1 root operator0, 89 Apr 15 14:14 /dev/ugen1 crwxrwxrwx 1 root operator0, 90 Apr 15 14:14 /dev/ugen1.1 crwxrwxrwx 1 root operator0, 91 Apr 16 01:34 /dev/ugen1.2 crwxrwxrwx 1 root operator0, 92 Apr 15 14:14 /dev/ugen1.3 usbdevs -vd Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 uhub0 port 1 powered port 2 addr 2: low speed, power 98 mA, config 1, USB Receiver(0xc521), Logitech(0x046d), rev 57.00 ums0 uhid0 Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 uhub1 port 1 powered port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 uhub2 port 1 addr 2: full speed, self powered, config 1, BCM2045B(0x2110), Broadcom Corp(0x0a5c), rev 1.00 ugen0 port 2 addr 3: full speed, power 100 mA, config 1, Biometric Coprocessor(0x2016), STMicroelectronics(0x0483), rev 0.01 ugen1 Controller /dev/usb3: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 uhub3 port 1 powered port 2 powered Controller /dev/usb4: addr 1: high speed, self powered, config 1, EHCI root hub(0x), Intel(0x), rev 1.00 uhub4 port 1 powered port 2 powered port 3 powered port 4 powered port 5 powered port 6 powered port 7 powered port 8 powered On Wed, Apr 16, 2008 at 2:43 AM, Simon Barner <[EMAIL PROTECTED]> wrote: > Outback Dingo wrote: > > pam_fprint works (see below) but when i try to run the fprint demo i get > > > > STATUS: No Devices Found > > Are you sure you have r/w access to the sensor's USB device? > > > > pam_fprint_enroll -f 7 > > This program will enroll your finger, unconditionally overwriting any > selected > > print that was enrolled previously. If you want to continue, press > enter, > > otherwise hit Ctrl+C > > > > Found device claimed by UPEK TouchStrip driver > > Opened device. It's now time to enroll your finger. > > > > You will need to successfully scan your Right Index Finger 3 times to > complete > > the process. > > > > Scan your finger now. > > upekts:error [read_msg] non-zero bytes in cmd response > > upekts:error [read_msg28] expected response, got -1 seq=40 > > Something seems to go wrong. I have never seenn this error message. > > Which sensor are you using? Can you send me the output of `usbdevs -vd' > in a private mail please? > > -- > Best regards / Viele Grüße, [EMAIL PROTECTED] > Simon Barner[EMAIL PROTECTED] > ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Openldap server install failure - openldap client conflict
Da Rock wrote: I'm trying to install OpenLDAP as a server to "attempt" to try it out for our network. The problem is the openldap client is already installed for other apps as php, apache, asterisk, etc. So my question is: is it possible to uninstall the client? Will the server include the client required for these other apps? The client installs libldap.so and liblber.so (plus variants based on OpenLDAP version and ABI version) -- like so for OpenLDAP 2.3: /usr/local/lib/liblber-2.3.so /usr/local/lib/liblber-2.3.so.2 /usr/local/lib/liblber.a /usr/local/lib/liblber.la /usr/local/lib/liblber.so /usr/local/lib/libldap-2.3.so /usr/local/lib/libldap-2.3.so.2 /usr/local/lib/libldap.a /usr/local/lib/libldap.la /usr/local/lib/libldap.so /usr/local/lib/libldap_r-2.3.so /usr/local/lib/libldap_r-2.3.so.2 /usr/local/lib/libldap_r.a /usr/local/lib/libldap_r.la /usr/local/lib/libldap_r.so (OpenLDAP 2.4 does similarly except replace '2.3' with '2.4') If you force uninstall openldap-client, then everything depending on it will refuse to run because of the unfulfilled shlib dynamic linkage. One of the programs that depends on the client is OpenLDAP-server -- so just by typing portinstall net/openldap23-server you'll cause openldap23-client (or openldap23-sasl-client) to be installed as a normal consequence of ports dependency resolution. The problem comes if you've already got, say, openldap23-client installed and you want openldap24-client -- other applications: Apache, PHP etc. will work with just about any LDAP version but openldap-server needs the matching client version. The solution is something like this: # portupgrade -o net/openldap24-client -f openldap-client-2.3.41 # portupgrade -fr openldap-client-2.4.8 to switch from the 23 series to the 24 series. Also -- handy tip -- adding flags like the following to /etc/make.conf will generally enable LDAP and SASL capabilities for any ports that can support them. (SASL highly recommended for securing access to LDAP, and also LDAP highly recommended as a back-end for SASL...) WITH_SASL= yes WITH_LDAP= yes WANT_OPENLDAP_VER= 23 WANT_OPENLDAP_SASL= yes However, don't insert the 'WANT_OPENLDAP_VER' line into /etc/make.conf until /after/ you've got the right openldap-client port installed, as it screws up switching between versions. 23 is the default stable release, 24 is also available but still in beta. And while I'm here... I tried installing the odbc backend, but it conflicts with other apps as well. How can I have both the libiodbc and unixodbc at the same time for openldap server (requires libiodbc), php5, etc? Do you really need the odbc *backend* for LDAP? That allows LDAP to store its data in a MSSQL database somewhere -- which implies the data store is on a different server to the OpenLDAP instance. That's not ideal for good performance. Unless you know you have a specific need for one of the particular back-ends and certainly if you are a beginner with openldap, I'd strongly recommend sticking with the default local storage based on Berkeley DB. If your aim is to interoperate with ActiveDirectory then I believe that is possible at the LDAP level via the usual delegation and referral mechanisms. It may even be possible to replicate either to or from AD or to use OpenLDAP (+ Kerberos + Samba v4 I think) as a drop in replacement for AD. I have no direct knowledge of that, but I'm sure a little Google action will turn up any number of HowTos on the subject. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: fprint (finger print sensor framework) port ready for testing
Fredrik Lindberg wrote: > Simon Barner wrote: >> Vladimir Grebenschikov wrote: >>> ???Have you seen/reviewed security/bioapi and security/bsp_upektfmess >>> (later works only on RELENG_6 now) ? >> Yes. In the mean time, there even is a binary of the UPEK driver for >> FreeBSD 7 i386, but the pam module did not work for me. > > A new binary has been re-rolled which takes care of the Undefined > symbol errors in the first one. It works with PAM as well. > The updated port can be found in ports/122768 Ok, good to know, I'll take care of your PR. > > However, if fprint suites your needs I would recommend using it instead. > Another possibility would be to create BioAPI modules based on the > reversed engineered code from fprint. The latter option might be interesting. However, the fprint developers plan more advanced authentication (and also identification) in the future (see link in my mail to Vladimir Grebenschikov earlier in this thread). -- Best regards / Viele Grüße, [EMAIL PROTECTED] Simon Barner[EMAIL PROTECTED] pgp5G8RWJgpBQ.pgp Description: PGP signature
Re: lzma (Re: HEADS UP: upgrading ImageMagick to 6.4.0-6)
On Tue, Apr 15, 2008 at 10:35:30PM -0400, Mikhail Teterin wrote: > 15 ??? 2008 10:21 ??, Brooks Davis ?? : > > Sadly, the author's licensing terms will limit the adoption of lzma. > > The BSD license is well established as the most restrictive acceptable > > license for successful, widely adopted compression schemes. > > Ever seen the inside of gzip.c (the original)? General Public License is > certainly more restrictive than BSD's and yet we (and just about everyone > else under the sun) had it in the tree until very recently, when a direct > client of libz was imported. The fact that a licensing compromsise was once made in the face of an extremely poor competitor (compress not only performs badly on text, it significantly expands files gzip and bzip are perfectly capable of compressing) is largely irrelevent. The reality is that the significant improvements provided by lzma will be relegated to a niche until an implementation under a BSD-like license is available. Even RMS acknoledges this effect http://lwn.net/2001/0301/a/rms-ov-license.php3 I wouldn't necessicairly be opposed to seeing support for tar.lzma files in bsd.port.mk, but I don't think lzma has a signficant future if the licensing policy remains as is (i.e. complex and not clearly defined in the source files). -- Brooks pgptTES63WXOg.pgp Description: PGP signature
Openldap server install failure - openldap client conflict
I'm trying to install OpenLDAP as a server to "attempt" to try it out for our network. The problem is the openldap client is already installed for other apps as php, apache, asterisk, etc. So my question is: is it possible to uninstall the client? Will the server include the client required for these other apps? And while I'm here... I tried installing the odbc backend, but it conflicts with other apps as well. How can I have both the libiodbc and unixodbc at the same time for openldap server (requires libiodbc), php5, etc? Cheers ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
CFT: devel/directfb update to 1.1.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi guys, A patch to update devel/directfb to 1.1.1 is ready to be committed, but I would like to have some feedback first: The following patch updates devel/directfb, games/freesci (dependent) and www/links (dependent): http://www.gahr.ch/FreeBSD/patches/_pending/directfb_complete.diff Please apply the patch as follows: # cd /usr/ports # patch < directfb_complete.diff rebuild devel/directfb, games/freesci and www/links Any feedback is welcome! - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (FreeBSD) iEYEAREKAAYFAkgFP1UACgkQwMJqmJVx947UwwCdEh4SHcvAR+uoBVyEtbISTRC3 uzsAn10tnHNe+p4ljkucY9ohZ0Q5j0i+ =UJoo -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fprint (finger print sensor framework) port ready for testing
Simon Barner wrote: Vladimir Grebenschikov wrote: ???Have you seen/reviewed security/bioapi and security/bsp_upektfmess (later works only on RELENG_6 now) ? Yes. In the mean time, there even is a binary of the UPEK driver for FreeBSD 7 i386, but the pam module did not work for me. A new binary has been re-rolled which takes care of the Undefined symbol errors in the first one. It works with PAM as well. The updated port can be found in ports/122768 However, if fprint suites your needs I would recommend using it instead. Another possibility would be to create BioAPI modules based on the reversed engineered code from fprint. Fredrik Lindberg ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fprint (finger print sensor framework) port ready for testing
Outback Dingo wrote: > pam_fprint works (see below) but when i try to run the fprint demo i get > > STATUS: No Devices Found Are you sure you have r/w access to the sensor's USB device? > > pam_fprint_enroll -f 7 > This program will enroll your finger, unconditionally overwriting any selected > print that was enrolled previously. If you want to continue, press enter, > otherwise hit Ctrl+C > > Found device claimed by UPEK TouchStrip driver > Opened device. It's now time to enroll your finger. > > You will need to successfully scan your Right Index Finger 3 times to complete > the process. > > Scan your finger now. > upekts:error [read_msg] non-zero bytes in cmd response > upekts:error [read_msg28] expected response, got -1 seq=40 Something seems to go wrong. I have never seenn this error message. Which sensor are you using? Can you send me the output of `usbdevs -vd' in a private mail please? -- Best regards / Viele Grüße, [EMAIL PROTECTED] Simon Barner[EMAIL PROTECTED] pgpwYuaXnNhDB.pgp Description: PGP signature
Re: fprint (finger print sensor framework) port ready for testing
Vladimir Grebenschikov wrote: > As I understand, pam module requires user name first. > So there no way to make gdm/kdm/*dm just scan image, find apropriate > user and login him ? As far as I can tell, it currently is not supported, but somebody seems to work on it: http://www.mail-archive.com/[EMAIL PROTECTED]/msg00471.html > > ???Have you seen/reviewed security/bioapi and security/bsp_upektfmess > (later works only on RELENG_6 now) ? Yes. In the mean time, there even is a binary of the UPEK driver for FreeBSD 7 i386, but the pam module did not work for me. > > Looks like fprint ports are introduce one new bioapi ? Yes, but at it seems, the developers deliberated well about it: http://www.reactivated.net/fprint/wiki/FAQ#Why_no_BioAPI.3F -- Best regards / Viele Grüße, [EMAIL PROTECTED] Simon Barner[EMAIL PROTECTED] pgp2Sn07MHDTL.pgp Description: PGP signature
Re: ports/122783: [PATCH] editors/emacs: update to 22.2
On Wed, 16 Apr 2008 03:27:36 +0900 (JST), KIMURA Yasuhiro <[EMAIL PROTECTED]> wrote: > Hello. > > Would someone please try the patch of ports/122783? I made this patch > as following: > > 1. Change PORTVERSION to 22.2 and reset PORTREVISION to 0. > 2. Update distinfo by doing 'make makesum'. > 3. Remove obsolete patch-src-gmalloc.c. > 4. Fix pkg-plist. > 5. Adjust bsd.emacs.mk accordingly. Hi Yasuhiro-san, That sounds about right! Thanks for doing all that :) > Every step is generic for port update, no emacs-specific know-how is > required, and it works fine for me. But maintainer says installation > fails as bellow. > > I'm not familiar with build of emacs at all. So any suggestion or > solution is welcome. Hi Yasuhiro-san, Note that it's not the Emacs build that fails, but the libgiofam build. My ports tree is a couple of days old. I'll resync and try again :) It may be an artifact of the local ports tree I used, so it will be good to see if this is only a local problem for me. > From: Giorgos Keramidas <[EMAIL PROTECTED]> > Subject: Re: ports/122783: [PATCH] editors/emacs: update to 22.2 > Date: Tue, 15 Apr 2008 18:50:20 +0300 > >> On Tue, 15 Apr 2008 14:13:11 +0900 (JST), KIMURA Yasuhiro <[EMAIL >> PROTECTED]> wrote: >> > System: FreeBSD 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Mon Mar 31 >> > 14:10:51 JST 2008 i386 >> >> Something is missing... After patching a local checkout of the port, I >> can't install the copy I just built of editors/emacs. It fails with: >> >> cc -shared .libs/libgiofam_la-fam-helper.o >> .libs/libgiofam_la-fam-module.o >> .libs/libgiofam_la-gfamdirectorymonitor.o >> .libs/libgiofam_la-gfamfilemonitor.o -Wl,--rpath -Wl,/usr/local/lib >> -Wl,--rpath -Wl,/usr/local/lib -L/usr/local/lib >> /usr/local/lib/libintl.so -lgio-2.0 /usr/local/lib/libgobject-2.0.so >> /usr/local/lib/libglib-2.0.so /usr/local/lib/libfam.so -Wl,-soname >> -Wl,libgiofam.so -Wl,-retain-symbols-file -Wl,.libs/libgiofam.exp -o >> .libs/libgiofam.so >> /usr/bin/ld: cannot find -lgio-2.0 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports/122783: [PATCH] editors/emacs: update to 22.2
From: Giorgos Keramidas <[EMAIL PROTECTED]> Subject: Re: ports/122783: [PATCH] editors/emacs: update to 22.2 Date: Tue, 15 Apr 2008 22:02:50 +0300 > Hi Yasuhiro-san, > > Note that it's not the Emacs build that fails, but the libgiofam build. > My ports tree is a couple of days old. I'll resync and try again :) > > It may be an artifact of the local ports tree I used, so it will be good > to see if this is only a local problem for me. That's good news for me :-). Please update your port tree and try again. Regards. --- KIMURA Yasuhiro ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Néctares de perfeição | Fine wine excelle nce
A perfeição do vinho não nasce apenas por si. Amadurece, acarinha-se e experiencia-se individualmente no sabor de um néctar fino, de rara elegância e inesquecível requinte - um dos mais de 3000 que poderá encontrar na nossa casa, a Garrafeira Nacional. Ao longo de 80 anos de paixão e tradição enológicas, edificámos uma vasta e ancestral colecção de vinhos e espirituosos, das mais valiosas em Portugal, que colocamos ao seu dispor na nossa loja electrónica. Assim, convido-o a conhecer a nossa casa, no coração de Lisboa, ou à distância de um clique, onde lhe asseguro que se deleitará com uma prova de excelência. Cordialmente, Jaime Vaz https://www.garrafeiranacional.com/index.php?lang=pt -- Perfection is not inherent to wine. It ripens and evolves into a treasured experience basked in vibrant aromas, glorious textures and elegant flavours - an experience to be found in more than 3000 of the finest Portuguese and European wines at Garrafeira Nacional. 80 years of time-honoured vinous passion have shaped us as one of the most relished wine and spirits merchants in Portugal. Our extensive collection is available for your perusal at the Garrafeira Nacional online store. You can also come and visit us in person. Located in the very heart of Lisbon, our family-owned wine shop is sure to delight you in a taste of excellence. Yours faithfully, Jaime Vaz https://www.garrafeiranacional.com/index.php?lang=en Para se remover de futuros mailings carregue no seguinte link. http://www.maxmailing.com/pub/rm.php?u=15cf3287d5&l=1182&c=212&e=6598d5c12f5d130fa8d3189ffbdadf56 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports/122783: [PATCH] editors/emacs: update to 22.2
Hello. Would someone please try the patch of ports/122783? I made this patch as following: 1. Change PORTVERSION to 22.2 and reset PORTREVISION to 0. 2. Update distinfo by doing 'make makesum'. 3. Remove obsolete patch-src-gmalloc.c. 4. Fix pkg-plist. 5. Adjust bsd.emacs.mk accordingly. Every step is generic for port update, no emacs-specific know-how is required, and it works fine for me. But maintainer says installation fails as bellow. I'm not familiar with build of emacs at all. So any suggestion or solution is welcome. Regards. --- KIMURA Yasuhiro From: Giorgos Keramidas <[EMAIL PROTECTED]> Subject: Re: ports/122783: [PATCH] editors/emacs: update to 22.2 Date: Tue, 15 Apr 2008 18:50:20 +0300 > On Tue, 15 Apr 2008 14:13:11 +0900 (JST), KIMURA Yasuhiro <[EMAIL PROTECTED]> > wrote: > > System: FreeBSD 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Mon Mar 31 > > 14:10:51 JST 2008 i386 > > Something is missing... After patching a local checkout of the port, I > can't install the copy I just built of editors/emacs. It fails with: > > cc -shared .libs/libgiofam_la-fam-helper.o > .libs/libgiofam_la-fam-module.o > .libs/libgiofam_la-gfamdirectorymonitor.o > .libs/libgiofam_la-gfamfilemonitor.o -Wl,--rpath -Wl,/usr/local/lib > -Wl,--rpath -Wl,/usr/local/lib -L/usr/local/lib > /usr/local/lib/libintl.so -lgio-2.0 /usr/local/lib/libgobject-2.0.so > /usr/local/lib/libglib-2.0.so /usr/local/lib/libfam.so -Wl,-soname > -Wl,libgiofam.so -Wl,-retain-symbols-file -Wl,.libs/libgiofam.exp -o > .libs/libgiofam.so > /usr/bin/ld: cannot find -lgio-2.0 > ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: www/links port fails to build with DirectFB library
On 2008.04.15, at 13:01, Pietro Cerutti wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Adam Martin wrote: | To whom it might concern, | | I've started a rebuild of all ports, on my home system, and links | port failed, with the libdirectfb. I have fixed it -- the dependancy | line with the "libdirectfb" entry should be changed to "directfb". An update to directfb and thus to links is underway.. please be patient, it will be fixed soon! Okay, thanks. It was a bit annoying, since I'm reinstalling everything, and needed links. (It wasn't too bad, just took me a good 20 minutes, and a few futile rebuilds to figure out what was broken.) I'll be doing a portsnap fetch and update later today, so we'll see if it's fixed by then. :-) It won't matter that much since I have it installed, and it runs. (Haven't tried it with directfb yet, but I think it will work.) Next time, I'll also submit a PR, now that I know the "right way" to report problems like this. Cheers, -- ADAM David Alan Martin Filesystem and Storage Lab, SUNY Stony Brook ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: www/links port fails to build with DirectFB library
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Adam Martin wrote: | To whom it might concern, | | I've started a rebuild of all ports, on my home system, and links | port failed, with the libdirectfb. I have fixed it -- the dependancy | line with the "libdirectfb" entry should be changed to "directfb". An update to directfb and thus to links is underway.. please be patient, it will be fixed soon! | Regards, Best, | ADAM David Alan Martin - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (FreeBSD) iEYEAREKAAYFAkgE32cACgkQwMJqmJVx947XKQCgk0P+VSdUAIjC/54Wd6YFYZH1 4OgAn1UxP0W0KKvcN4KWjnIF42B6BJDC =q85c -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: what is gio-fam?
On Tue, 15 Apr 2008 02:38:48 -0500, Alexey Shuvaev <[EMAIL PROTECTED]> wrote: On Mon, Apr 14, 2008 at 10:31:18AM -0500, Jeremy Messenger wrote: On Mon, 14 Apr 2008 10:09:06 -0500, Jeremy Messenger <[EMAIL PROTECTED]> wrote: On Mon, 14 Apr 2008 03:50:09 -0500, Alexey Shuvaev <[EMAIL PROTECTED]> wrote: IMHO gio-fam-backend should not be implicit dependency. Otherwise why not to install all existing non-conflicting libraries just to ease maintainer's life :-> FWIW x11-toolkits/gtkdatabox2 (PR 116120) do not need gio-fam-backend. Well, all ports should depend on gio-fam-backend. The gio is included and part of glib20. marcus had to split gio out of glib20 package to avoid circle dependency of glib20 -> gamin (FAM replacement) -> glib20. If marcus doesn't split and you guys will have that gio library anyway. Thanks, somewhat much clearer now. I had some feeling that gio-fam-backend is freebsd specific. How many chances are there to account for existence of gamin upstream? (So to avoid glib -> gamin -> glib circular dependency) I had chat with marcus (included my team) to get more clear info for us. He said: Here's the deal. Glib 2.16 includes a lot of the file management code that was previously included in gnome-vfs. Part of that code is a file monitor wrapper which allows the new GIO subsystem to get real-time file update information. This wrapper has FAM, inotify, and Solaris backends. The only backend that works on FreeBSD is the FAM backend. If anyone is still complaining, then anyone can implement a GIO monitor using pure kqueue. This will get glib20 to not depend on FAM anymore. It can be take a lot of code from gamin. marcus has said a bit more: Since we couldn't have glib depend on FAM directly, I broke out this file monitor module into a separate port. Any port which depends on glib could use the GIO subsystem, and would need one of these file monitor modules to be fully functional. I thought it would be easier to just make ports that depend on glib20 automatically require this module so maintainers wouldn't have to check and see if their port used GIO. Fam/gamin are not big dependencies. Hell, they don't even take up memory unless used. Keep in mind, in the next major release of GTK+ depends on GIO. It's already in GTK+ SVN for depend on GIO, so it won't make any difference. Uh, I should have check in glib20 and gio-fam-backend before I made that comment. I thought that gio (libgio-2.0.so) is in gio-fam-backend, but not it's in glib20. The gio-fam-backend only installs libgiofam.so and FAM support is option in glib configure. I don't think it will be easy to make optional (maybe I am wrong) with that split. Remove gio-fam-backend dependency is going to hurt some users if they want some missing fuction(s) of it. So configure option is not enough. Nevermind about above for not think will be easy. I have taken a look more in gio-fam-backend and figured out to make optional. I am still discussing with my team (some disagree and agree), because make it optional will causing some reduced functionality in runtime. I am thinking about add something like WITHOUT_FAM_WARNING with better explain and users will know their choice to have functions reduced, so can't be report to us. IMO, I do still think add optional is a bit silly since GIO basicually already have similar function of gamin. It's just happen that there is no kqueue backend available for FreeBSD and forced us to get glib20 depends on FAM or gamin. I am kind of on fence to make it optional. Does separating gio-fam-backend by original developers solve the problem better? I think marcus's comments have answered to this. Cheers, Mezz Alexey. -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: www/links port fails to build with DirectFB library
Hey Adam-
I think the best course of action would be for you to correct the offending
lines in the Makefile and then open up a PR with the patch. After the
maintainer of the port approves the patch, it can be commited to cvs.
Thanks for catching this.
SK
On Tue, Apr 15, 2008 at 12:38:50AM -0400, Adam Martin wrote:
> To whom it might concern,
>
> I've started a rebuild of all ports, on my home system, and links
> port failed, with the libdirectfb. I have fixed it -- the dependancy
> line with the "libdirectfb" entry should be changed to "directfb".
>
> Line 51 (as of my last portsnap fetch; portsnap update, a few minutes
> ago) of /usr/ports/www/links/Makefile should read:
>
> LIB_DEPENDS+= directfb:${PORTSDIR}/devel/directfb
>
> Instead it reads:
>
> LIB_DEPENDS+= libdirectfb:${PORTSDIR}/devel/directfb
>
>
> Hopefully this hasn't affected too many people, and hopefully I'm not
> pestering the wrong people.
>
> Regards,
>
> --
> ADAM David Alan Martin
>
> Filesystem and Storage Lab, SUNY Stony Brook
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fprint (finger print sensor framework) port ready for testing
pam_fprint works (see below) but when i try to run the fprint demo i get STATUS: No Devices Found pam_fprint_enroll -f 7 This program will enroll your finger, unconditionally overwriting any selected print that was enrolled previously. If you want to continue, press enter, otherwise hit Ctrl+C Found device claimed by UPEK TouchStrip driver Opened device. It's now time to enroll your finger. You will need to successfully scan your Right Index Finger 3 times to complete the process. Scan your finger now. upekts:error [read_msg] non-zero bytes in cmd response upekts:error [read_msg28] expected response, got -1 seq=40 Enroll stage passed. Yay! Scan your finger now. Enroll stage passed. Yay! Scan your finger now. Enroll complete! Enrollment completed! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
compatibility with installed ports (Re: what is gio-fam?)
вівторок 15 квітень 2008 10:43 до, Ricardo Nabinger Sanchez Ви написали: > > Going forward, one hopes, gnome-team will not be so cavalier in forcing > > upgrades... > > How about working with the gnome-team instead of blaming them? I'd bet > that if you had to upgrade Gnome by hand, you would be using KDE or > something else. Yes, yes. We have to come to this point, don't we? After several attempts are made at defending a blunder, an indignant request is made for the complaining party to help the culprit (even if an /explicit/ aknowledgement of the blunder is yet to appear)... Gnome@ is a team. They are not lacking in resources, AFAIK. The author of tinderbox is a prominent member, for crying out loud! The problem is the "philosophy". I readily admit, that their work is vast, but the "all your ports are belong to us" and the "portupgrade is easy, so shut up" attitude is not something, that "working with the gnome-team" can help with... Meanwhile, judging from what can be gathered from their mailing lists, the KDE@ team is working hard to ensure peaceful co-existence of KDE3 and KDE4 ports... > Shouting at gnome-team won't help at all. Pointing out a problem sometimes helps prevent it from reoccuring or, at least, reduce the frequency/severety of the reoccurance(s). Sometimes it also helps fix the current instance... -mi ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: what is gio-fam?
On Tue, 15 Apr 2008 10:03:18 -0400 Mikhail Teterin <[EMAIL PROTECTED]> wrote: > вівторок 15 квітень 2008 08:55 до, Ricardo Nabinger Sanchez Ви написали: > > Not quite. I also faced this, but was lucky to discover in time (not > > closing any open app) where this dependency was coming from. The only port > > I had to update was glib, a couple of times, and gio-fam was finally built. > > > This was instinctive, but worked. > > "A couple of times"? Congratulations... Thanks. > > One should not need this luck, nor this instinct, however. It wasn't luck, I usually upgrade a few ports before launching a bunch of upgrades. Glib build broke during some other port upgrade, and I checked what happened. Updated its dependencies, itself forcibly, and then resumed the other port. > > Until I decide to upgrade gnome, all other gnome-using ports should be > content > with the version of gnome I already have... > > This is all patently obvious, I might add. The automatic gio-fam dependency > should be made smarter and/or optional (depending on which gnome is already > installed). > > Going forward, one hopes, gnome-team will not be so cavalier in forcing > upgrades... How about working with the gnome-team instead of blaming them? I'd bet that if you had to upgrade Gnome by hand, you would be using KDE or something else. Shouting at gnome-team won't help at all. -- Ricardo Nabinger Sanchez [EMAIL PROTECTED] http://rnsanchez.wait4.org "Left to themselves, things tend to go from bad to worse." ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: what is gio-fam?
вівторок 15 квітень 2008 08:55 до, Ricardo Nabinger Sanchez Ви написали: > Not quite. I also faced this, but was lucky to discover in time (not > closing any open app) where this dependency was coming from. The only port > I had to update was glib, a couple of times, and gio-fam was finally built. > This was instinctive, but worked. "A couple of times"? Congratulations... One should not need this luck, nor this instinct, however. Until I decide to upgrade gnome, all other gnome-using ports should be content with the version of gnome I already have... This is all patently obvious, I might add. The automatic gio-fam dependency should be made smarter and/or optional (depending on which gnome is already installed). Going forward, one hopes, gnome-team will not be so cavalier in forcing upgrades... -mi ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: what is gio-fam?
On Mon, 14 Apr 2008 18:43:22 -0400 Mikhail Teterin <[EMAIL PROTECTED]> wrote: > No, thanks. I want the most recent version /of the port/. And the port itself > does not care, which version of GNOME it is built against -- it is happy, > with /what I already have/ (earlier GNOME). Yet, I'm forced to upgrade, what > I already have -- gratuicously... Not quite. I also faced this, but was lucky to discover in time (not closing any open app) where this dependency was coming from. The only port I had to update was glib, a couple of times, and gio-fam was finally built. This was instinctive, but worked. -- Ricardo Nabinger Sanchez [EMAIL PROTECTED] http://rnsanchez.wait4.org "Left to themselves, things tend to go from bad to worse." ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Building 'gvfs'
On Mon, Apr 14, 2008 at 6:12 AM, Gerard <[EMAIL PROTECTED]> wrote: > FreeBSD-6.3 > > I have attempted to update to 'gvfs-0.2.3_2'. I have not modified the > configuration file in any way. In fact, I even ran 'make rmconfig' to insure > that it was not affecting the build. However, the update continually fails. > 'gvfs' claims it wants 'cdio_paranoia.0' installed. > > I have 'libcdio-0.78.2_1' installed with the basic configuration file. I was > forced to modify the configuration file, check 'PARANOIA', and rebuild the > port in order to get 'gvfs' to build. > > This does not seem correct. I suppose that I could have also modified the > 'gvfs' configuration file; however, neither should be required to do a basic > port installation. I believe the 'gvfs' port should be modified. > > Am I overlooking something here? > By default sysutils/libcdio has PARANOIA enabled. Looks like you had installed sysutils/libcdio without PARANOIA enabled, and then tried to install devel/gvfs with CDDA enabled. Which required PARANOIA to be enabled in sysutils/libcdio. The ports system isn't smart enough to know PARANOIA needed to be enabled in sysutils/libcdio, inorder to build devel/gvfs with CDDA enabled. One possible solution is to add the following to devel/gvfs/Makefile: OPTION_DEPEND= devel/libcdio:WITH_PARANOIA and then have bsd.ports.mk check if WITH_PARANOIA is enabled, if not enabled give a warning to rebuild the devel/libcdio port with PARANOIA enabled. Scot ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fprint (finger print sensor framework) port ready for testing
On Mon, 2008-04-14 at 20:07 +0200, Simon Barner wrote: > Hi, > > I did a port [2] of the fprint finger print sensor framework [1] > and would like to receive some feedback before I commit it. > > It comes with a PAM module for finger print based authentication, a > graphical (fprint_demo) and a console (pam_fprint_enroll) application > for finger print enrollment. > > I did my tests with the UPEK sensor found in Lenovo's T61. Cool, it works for me, even pam module. As I understand, pam module requires user name first. So there no way to make gdm/kdm/*dm just scan image, find apropriate user and login him ? Have you seen/reviewed security/bioapi and security/bsp_upektfmess (later works only on RELENG_6 now) ? Looks like fprint ports are introduce one new bioapi ? > Simon > > (M'fup2 ports@) > > [1] http://www.reactivated.net/fprint/wiki/Main_Page > [2] http://home.leo.org/~barner/freebsd/fprint.tar.gz > -- Vladimir B. Grebenschikov [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fprint (finger print sensor framework) port ready for testing
On Apr 14, 2008, at 8:07 PM, Simon Barner wrote: I did a port [2] of the fprint finger print sensor framework [1] and would like to receive some feedback before I commit it. It comes with a PAM module for finger print based authentication, a graphical (fprint_demo) and a console (pam_fprint_enroll) application for finger print enrollment. I did my tests with the UPEK sensor found in Lenovo's T61. Well done ! Works with the VAIO fps just fine. Dw ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fprint (finger print sensor framework) port ready for testing
On Mon, 2008-04-14 at 20:07 +0200, Simon Barner wrote: > Hi, > > I did a port [2] of the fprint finger print sensor framework [1] > and would like to receive some feedback before I commit it. > > It comes with a PAM module for finger print based authentication, a > graphical (fprint_demo) and a console (pam_fprint_enroll) application > for finger print enrollment. > > I did my tests with the UPEK sensor found in Lenovo's T61. > > Simon > > (M'fup2 ports@) > > [1] http://www.reactivated.net/fprint/wiki/Main_Page > [2] http://home.leo.org/~barner/freebsd/fprint.tar.gz > This is fantastic! People have always been asking me 'so does the fingerprint sensor work?' when they find out I run FreeBSD on my laptop - and now I can tell them it does! Just tested with fprint_demo, but successfully enrolled and verified my fingerprints no problem, using an HP nc6320 and the aes2501 sensor. Cheers Tom signature.asc Description: This is a digitally signed message part
Re: vsftpd-2.0.6 failed to compile on FreeBSD-4.11-p26
On Tue, Apr 15, 2008 at 09:24:43AM +0800, John/SML wrote: >Then, I think the appropriate way to keep up with port updates is to >upgrade from FreeBSD 4.11 to FreeBSD 7. However, it is possible to use the >"build world" method to upgrade from 4.11 to 7, or I have to use the >binary upgrade method by using the FreeBSD 7 CD media. I'll second Mark's recommendation to re-install rather than attempt a source upgrade. Note that, whilst your 4.x ports tree will continue to work with 7.x (assuming you have the relevant compat4x libraries), you will need to do a complete ports rebuild as soon as you upgrade any port (pretty much). (Otherwise, you will wind up linking against different versions of the same system libraries - a recipe for disaster). -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgpTR5F168mga.pgp Description: PGP signature
porting software with Linux netlink(3)
Hello!. I want to update palm/synce-* ports and get some problems while porting odccm from synce project. Is there any chance to get netlink(3) on FreeBSD? Here is some logs: checking for pkg-config... /usr/local/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for LIBSYNCE... yes checking for GLIB... yes checking for GNET... yes checking for DBUS... yes checking for HAL... yes configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating tests/Makefile config.status: creating man/Makefile config.status: executing depfiles commands ===> Building for synce-odccm-0.11 Making all in src make all-am cc -DPACKAGE_NAME=\"odccm\" -DPACKAGE_TARNAME=\"odccm\" -DPACKAGE_VERSION=\"0.11\" -DPACKAGE_STRING=\"odccm\ 0.11\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"odccm\" -DVERSION=\"0.11\" -DSTDC_HEADERS=1 -DENABLE_LEGACY_SUPPORT=1 -I. -Wall -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -D_REENTRANT -I/usr/local/include/gnet-2.0 -I/usr/local/lib/gnet-2.0/include/ -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/local/include/hal -I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include -O2 -fno-strict-aliasing -pipe -MT odccm-device-signals-marshal.o -MD -MP -MF .deps/odccm-device-signals-marshal.Tpo -c -o odccm-device-signals-marshal.o odccm-device-signals-marshal.c mv -f .deps/odccm-device-signals-marshal.Tpo .deps/odccm-device-signals-marshal.Po cc -DPACKAGE_NAME=\"odccm\" -DPACKAGE_TARNAME=\"odccm\" -DPACKAGE_VERSION=\"0.11\" -DPACKAGE_STRING=\"odccm\ 0.11\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"odccm\" -DVERSION=\"0.11\" -DSTDC_HEADERS=1 -DENABLE_LEGACY_SUPPORT=1 -I. -Wall -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -D_REENTRANT -I/usr/local/include/gnet-2.0 -I/usr/local/lib/gnet-2.0/include/ -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/local/include/hal -I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include -O2 -fno-strict-aliasing -pipe -MT odccm-device-manager-signals-marshal.o -MD -MP -MF .deps/odccm-device-manager-signals-marshal.Tpo -c -o odccm-device-manager-signals-marshal.o odccm-device-manager-signals-marshal.c mv -f .deps/odccm-device-manager-signals-marshal.Tpo .deps/odccm-device-manager-signals-marshal.Po cc -DPACKAGE_NAME=\"odccm\" -DPACKAGE_TARNAME=\"odccm\" -DPACKAGE_VERSION=\"0.11\" -DPACKAGE_STRING=\"odccm\ 0.11\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"odccm\" -DVERSION=\"0.11\" -DSTDC_HEADERS=1 -DENABLE_LEGACY_SUPPORT=1 -I. -Wall -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -D_REENTRANT -I/usr/local/include/gnet-2.0 -I/usr/local/lib/gnet-2.0/include/ -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/local/include/hal -I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include -O2 -fno-strict-aliasing -pipe -MT util.o -MD -MP -MF .deps/util.Tpo -c -o util.o util.c mv -f .deps/util.Tpo .deps/util.Po cc -DPACKAGE_NAME=\"odccm\" -DPACKAGE_TARNAME=\"odccm\" -DPACKAGE_VERSION=\"0.11\" -DPACKAGE_STRING=\"odccm\ 0.11\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"odccm\" -DVERSION=\"0.11\" -DSTDC_HEADERS=1 -DENABLE_LEGACY_SUPPORT=1 -I. -Wall -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -D_REENTRANT -I/usr/local/include/gnet-2.0 -I/usr/local/lib/gnet-2.0/include/ -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/local/include/hal -I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include -O2 -fno-strict-aliasing -pipe -MT odccm-errors.o -MD -MP -MF .deps/odccm-errors.Tpo -c -o odccm-errors.o odccm-errors.c mv -f .deps/odccm-errors.Tpo .deps/odccm-errors.Po cc -DPACKAGE_NAME=\"odccm\" -DPACKAGE_TARNAME=\"odccm\" -DPACKAGE_VERSION=\"0.11\" -DPACKAGE_STRING=\"odccm\ 0.11\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"odccm\" -DVERSION=\"0.11\" -DSTDC_HEADERS=1 -DENABLE_LEGACY_SUPPORT=1 -I. -Wall -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -D_REENTRANT -I/usr/local/include/gnet-2.0 -I/usr/local/lib/gnet-2.0/include/ -I/usr/local/include/glib-2.0 -I/usr/loca
Update to net-mgmt/arts++
Hello, we have an updated version of the arts++ package which fixes the compilation problems with GCC 4.x. The latest version is at http://www.caida.org/tools/utilities/arts/download/arts++-1.1.a13.tar.gz Please let me know if you need any additional information. -- [EMAIL PROTECTED] (Ryan Koga) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
porting software with Linux netlink(3)
Hello!. I want to update palm/synce-* ports and get some problems while porting odccm from synce project. Is there any chance to get netlink(3) on FreeBSD? Here is some logs: checking for pkg-config... /usr/local/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for LIBSYNCE... yes checking for GLIB... yes checking for GNET... yes checking for DBUS... yes checking for HAL... yes configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating tests/Makefile config.status: creating man/Makefile config.status: executing depfiles commands ===> Building for synce-odccm-0.11 Making all in src make all-am cc -DPACKAGE_NAME=\"odccm\" -DPACKAGE_TARNAME=\"odccm\" -DPACKAGE_VERSION=\"0.11\" -DPACKAGE_STRING=\"odccm\ 0.11\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"odccm\" -DVERSION=\"0.11\" -DSTDC_HEADERS=1 -DENABLE_LEGACY_SUPPORT=1 -I. -Wall -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -D_REENTRANT -I/usr/local/include/gnet-2.0 -I/usr/local/lib/gnet-2.0/include/ -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/local/include/hal -I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include -O2 -fno-strict-aliasing -pipe -MT odccm-device-signals-marshal.o -MD -MP -MF .deps/odccm-device-signals-marshal.Tpo -c -o odccm-device-signals-marshal.o odccm-device-signals-marshal.c mv -f .deps/odccm-device-signals-marshal.Tpo .deps/odccm-device-signals-marshal.Po cc -DPACKAGE_NAME=\"odccm\" -DPACKAGE_TARNAME=\"odccm\" -DPACKAGE_VERSION=\"0.11\" -DPACKAGE_STRING=\"odccm\ 0.11\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"odccm\" -DVERSION=\"0.11\" -DSTDC_HEADERS=1 -DENABLE_LEGACY_SUPPORT=1 -I. -Wall -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -D_REENTRANT -I/usr/local/include/gnet-2.0 -I/usr/local/lib/gnet-2.0/include/ -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/local/include/hal -I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include -O2 -fno-strict-aliasing -pipe -MT odccm-device-manager-signals-marshal.o -MD -MP -MF .deps/odccm-device-manager-signals-marshal.Tpo -c -o odccm-device-manager-signals-marshal.o odccm-device-manager-signals-marshal.c mv -f .deps/odccm-device-manager-signals-marshal.Tpo .deps/odccm-device-manager-signals-marshal.Po cc -DPACKAGE_NAME=\"odccm\" -DPACKAGE_TARNAME=\"odccm\" -DPACKAGE_VERSION=\"0.11\" -DPACKAGE_STRING=\"odccm\ 0.11\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"odccm\" -DVERSION=\"0.11\" -DSTDC_HEADERS=1 -DENABLE_LEGACY_SUPPORT=1 -I. -Wall -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -D_REENTRANT -I/usr/local/include/gnet-2.0 -I/usr/local/lib/gnet-2.0/include/ -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/local/include/hal -I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include -O2 -fno-strict-aliasing -pipe -MT util.o -MD -MP -MF .deps/util.Tpo -c -o util.o util.c mv -f .deps/util.Tpo .deps/util.Po cc -DPACKAGE_NAME=\"odccm\" -DPACKAGE_TARNAME=\"odccm\" -DPACKAGE_VERSION=\"0.11\" -DPACKAGE_STRING=\"odccm\ 0.11\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"odccm\" -DVERSION=\"0.11\" -DSTDC_HEADERS=1 -DENABLE_LEGACY_SUPPORT=1 -I. -Wall -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -D_REENTRANT -I/usr/local/include/gnet-2.0 -I/usr/local/lib/gnet-2.0/include/ -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/local/include/hal -I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include -O2 -fno-strict-aliasing -pipe -MT odccm-errors.o -MD -MP -MF .deps/odccm-errors.Tpo -c -o odccm-errors.o odccm-errors.c mv -f .deps/odccm-errors.Tpo .deps/odccm-errors.Po cc -DPACKAGE_NAME=\"odccm\" -DPACKAGE_TARNAME=\"odccm\" -DPACKAGE_VERSION=\"0.11\" -DPACKAGE_STRING=\"odccm\ 0.11\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"odccm\" -DVERSION=\"0.11\" -DSTDC_HEADERS=1 -DENABLE_LEGACY_SUPPORT=1 -I. -Wall -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -D_REENTRANT -I/usr/local/include/gnet-2.0 -I/usr/local/lib/gnet-2.0/include/ -I/usr/local/include/glib-2.0 -I/usr/loca
Re: what is gio-fam?
On Mon, Apr 14, 2008 at 10:31:18AM -0500, Jeremy Messenger wrote: > On Mon, 14 Apr 2008 10:09:06 -0500, Jeremy Messenger <[EMAIL PROTECTED]> > wrote: > >> On Mon, 14 Apr 2008 03:50:09 -0500, Alexey Shuvaev >> <[EMAIL PROTECTED]> wrote: >> >> >>> IMHO gio-fam-backend should not be implicit dependency. Otherwise why >>> not to install all existing non-conflicting libraries just to ease >>> maintainer's life :-> >>> FWIW x11-toolkits/gtkdatabox2 (PR 116120) do not need gio-fam-backend. >> >> Well, all ports should depend on gio-fam-backend. The gio is included and >> part of glib20. marcus had to split gio out of glib20 package to avoid >> circle dependency of glib20 -> gamin (FAM replacement) -> glib20. If >> marcus doesn't split and you guys will have that gio library anyway. Thanks, somewhat much clearer now. I had some feeling that gio-fam-backend is freebsd specific. How many chances are there to account for existence of gamin upstream? (So to avoid glib -> gamin -> glib circular dependency) > > Uh, I should have check in glib20 and gio-fam-backend before I made that > comment. I thought that gio (libgio-2.0.so) is in gio-fam-backend, but not > it's in glib20. The gio-fam-backend only installs libgiofam.so and FAM > support is option in glib configure. I don't think it will be easy to make > optional (maybe I am wrong) with that split. Remove gio-fam-backend > dependency is going to hurt some users if they want some missing fuction(s) > of it. > So configure option is not enough. Does separating gio-fam-backend by original developers solve the problem better? Alexey. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
