Re: pkg 1.3.8 requested but not available?
Le 23/09/2014 11:44, Michelle Sullivan a écrit : > Florent Peterschmitt wrote: >> Le 23/09/2014 11:02, Michelle Sullivan a écrit : >> >>> Baptiste Daroussin wrote: >>> >>>> [...] >>>> You are using portupgrade so first upgrade pkg with portupgrade >>>> >>>> >>>> >>> Just a thought here - why (like .rpm and .deb - and the reason I hate >>> them so much) are you making the package manager version a dependency of >>> a package? I can understand if there are new features that you may need >>> to use a later version to get those features, but making a package >>> dependent on the package manager rather than displaying a warning that a >>> feature is missing is the brain dead way that plagues upgrades for >>> redhat and debian. Of course if your intent is to make FreeBSD into >>> another Linux distro just with a different kernel, continue. >>> >>> >> >> What is the problem of upgrading the package manager first and then >> upgrade the rest of the world without any problem? >> >> > Not disagreeing with you... but making dependencies like this leads to > everything relying on the package manager being a particular version.. > which in my opinion is wrong... the package manager is not part of the > software you're installing... and shouldn't be part of a dependency tree > - particularly when building your own ports. This makes sense. > *Every* time a Redhat and Debian system screwed up that I have had, was > caused by the package manager needing to be updated before a particular > package, then all the other dependent packages needed to be upgraded, > and the libraries and you end up with the catch 22 of the package > manager can't be installed because the package manager is too old and > you end up with a half working system that needs to be re-installed > because you needed to apply a security fix to a perl module! Now > FreeBSD has one advantage (currently) ... the package manager is not > part of the OS, it in itself is a port.. however that has half changed > already and in what, another month? it's going to be part of the OS... Yes but it doesn't manage the system, only port packages. > Yeah sure keep building pkg-static so it can be installed independently, > but be aware that one does not want to get into dependency loops or > having to upgrade everything just for one security fix - particularly > when working with the ports tree and not the package manager... some > people have production servers that need a security fix, not an upgrade > of everything. > I'm curious to know how you get into this mess with Debian or RH distros. What version of these distros? And are you sure it is impossible to uprade only the PM (package manager) and keep other packages like they currently are? Never had to reinstall a system for a security upgrade because of dependency loop. Sounds very strange to me. signature.asc Description: OpenPGP digital signature
Re: pkg 1.3.8 requested but not available?
Le 23/09/2014 11:02, Michelle Sullivan a écrit : > Baptiste Daroussin wrote: >> [...] >> You are using portupgrade so first upgrade pkg with portupgrade >> >> > > Just a thought here - why (like .rpm and .deb - and the reason I hate > them so much) are you making the package manager version a dependency of > a package? I can understand if there are new features that you may need > to use a later version to get those features, but making a package > dependent on the package manager rather than displaying a warning that a > feature is missing is the brain dead way that plagues upgrades for > redhat and debian. Of course if your intent is to make FreeBSD into > another Linux distro just with a different kernel, continue. > What is the problem of upgrading the package manager first and then upgrade the rest of the world without any problem? signature.asc Description: OpenPGP digital signature
Re: Screen vertical split
Le 28/12/2013 17:07, Zsolt Udvari a écrit : > 2013/12/28 James Griffin : >> yeah, it's in the docs I found online, although not in the man page on >> FreeBSD. > Ahh. I don't find it in FreeBSD's manpage. > I'm using tmux but installed now screen and as I see there's not vertical > split. What version of FreeBSD and Screen/Tmux are you using? I can do a vertical split with Tmux 1.7/1.8 (dont know for screen) and FreeBSD 9/10 -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | * Trim your quotations. Really. Proudly powered by Open Source | Thank you :) signature.asc Description: OpenPGP digital signature
Re: lang/php5 - separate apache module from php5 port
On 23/11/13 13:20, geoffroy desvernay wrote: > On 12/07/2013 14:57, Florent Peterschmitt wrote: >> Le 10/07/2013 23:54, olli hauer a écrit : >>>> Here it would be ap22-mod_php5 and ap24-mod_php5. >>>> >>> >>> Thats what I thought with your first mail and I suspect this is a good idea. >> >> Yep, it was what I meant. So do you think I should contact the maintainer ? >> > I second this, as php-fpm is more and more used, with apache, nginx, > lighttpd... There are also cases where only php-cli is needed (at least > we use that too) > > I like the way debian handle this: php-cli/php-fpm/php-cgi/php-module > are packaged independently (and in freebsd we could have ap22-mod-php > and ap24-mod-php). > > The difficulty may be that it would make some more ports to maintain for > Alex, who may need some help (?) > > My 2 cts... > > ps: re-using this thread as I didn't find (missed?) any more recent > discussion about this... > Yeah, Debian's package split is nice (and not only for PHP but everything else). But I'm not sure if we want to make x packages we have to make x ports. I mean, it is very useful when distributing packages and I'm not sure the port system cannot make x packages from 1 only port. -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | * Trim your quotations. Really. Proudly powered by Open Source | Thank you :) signature.asc Description: OpenPGP digital signature
Re: FreeBSD mplayer port update?
On 08/10/2013 18:18, Ronald F. Guilmette wrote: > If I knew that my mplayer > had been updated recently, then I would tend more to suspect the video > file of being corrupted. Have you tried another player? -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | * Trim your quotations. Really. Proudly powered by Open Source | Thank you :) signature.asc Description: OpenPGP digital signature
Re: port missing dep.!
Le 08/10/2013 14:51, K.C. Smith a écrit : > The port sysutils / linux-afaapps-2.7_4 is missing a dependency, > namely devel / linux-f10-ncurses-base-5.6. Please fill a PR. The subject of the mail isn't helpful. -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | * Trim your quotations. Really. Proudly powered by Open Source | Thank you :) signature.asc Description: OpenPGP digital signature
Re: Can't compile www/chromium on 9.2-RC1
Le 02/10/2013 09:19, Florent Peterschmitt a écrit : > My advise is to reinstall world with clang :) Or select GCC 4.6+ to build this port in www/chromium options. -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | * Trim your quotations. Really. Proudly powered by Open Source | Thank you :) signature.asc Description: OpenPGP digital signature
Re: Can't compile www/chromium on 9.2-RC1
Le 02/10/2013 02:57, George Mitchell a écrit : > It tries to compile with clang, which I don't have on my 9.2-RC1 box. [snip] > What's the next thing to do? Reinstall world with clang? It's been a long time www/chromium doesn't build with base's. More and more ports are not building with base's GCC so not having clang will juste bring some headaches. Also, the www/chromium port can use clang from ports if the version < 902000. Seems that 9.2-RC1 is up to this version. My advise is to reinstall world with clang :) -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | * Trim your quotations. Really. Proudly powered by Open Source | Thank you :) signature.asc Description: OpenPGP digital signature
Re: vim syntax headers
Le 02/09/2013 18:30, Michael Schuh a écrit : > should work since vim 6.0; > may be modelines are disabled per default for security concerns? Yep, someone found the solution and then I searched for the answer about modelines and found security problems. I read[0] that modelines are just able to do "set" work. So I think using modelines is safe now and the default behaviour can be changed, or documented at installation. What do you -all- think about it? [0] http://usevim.com/2012/03/28/modelines/ -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | * Trim your quotations. Really. Proudly powered by Open Source | Thank you :) signature.asc Description: OpenPGP digital signature
Re: vim syntax headers
Le 02/09/2013 14:22, olli hauer a écrit : > perhaps modline is disabled? > > echo 'set modeline' >> ~/.vimrc You rock! Thanks for this :) -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | * Trim your quotations. Really. Proudly powered by Open Source | Thank you :) signature.asc Description: OpenPGP digital signature
Re: vim syntax headers
Le 02/09/2013 12:27, Serpent7776 a écrit : > Try this: > # vim: set syntax=apache Doesn't work anymore. I built vim 7.4 manually (and installed it in ~/.local), it doesn't work anymore but it's ok on Debian with vim 7.4. A bug somewhere? -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | * Trim your quotations. Really. Proudly powered by Open Source | Thank you :) signature.asc Description: OpenPGP digital signature
Re: vim syntax headers
Le 02/09/2013 12:20, Pietro Cerutti a écrit : > try with > > # vim: ft=apache No more results. -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | * Trim your quotations. Really. Proudly powered by Open Source | Thank you :) signature.asc Description: OpenPGP digital signature
vim syntax headers
Hi, I want to use this header (or footer) to tell vim showing syntax highliting on Apache conf files: # vim: syntax=apache If put at head of file, only the comment will be colored, not the text. If put at the end of fiel, nothing is colored. Then if a :set syntax=apache, syntax goes on. Here is vimrc I use: http://projet.beastie.eu/?p=desktop-config.git;a=blob_plain;f=vimrc;hb=HEAD Any idea? -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | * Trim your quotations. Really. Proudly powered by Open Source | Thank you :) signature.asc Description: OpenPGP digital signature
Re: CFT: vlc 2.0.8 (with two PRs applied)
Le 30/08/2013 15:52, Gary Jennejohn a écrit : > So, one report of success. And a second too. Except the problem with Xvideo choosen by default and don't work with me, it's all right. -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | * Trim your quotations. Really. Proudly powered by Open Source | Thank you :) signature.asc Description: OpenPGP digital signature
Re: Fwd: Re: CFT: vlc 2.0.8 (with two PRs applied)
Le 29/08/2013 21:16, Juergen Lock a écrit : > Hm is vesa even supposed to support xv? I really don't know :D > Also have you tried xv with another player like mplayer -vo xv ? Here is the output (from the ATI machine): % mplayer -vo xv 46\ Le\ Code\ de\ chevalerie.mkv […] [VO_XV] It seems there is no Xvideo support for your video card available. [VO_XV] Run 'xvinfo' to verify its Xv support and read [VO_XV] DOCS/HTML/en/video.html#xv! [VO_XV] See 'mplayer -vo help' for other (non-xv) video out drivers. [VO_XV] Try -vo x11. Error opening/initializing the selected video_out (-vo) device. It runs well with -vo x11 -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | * Trim your quotations. Really. Proudly powered by Open Source | Thank you :) signature.asc Description: OpenPGP digital signature
Re: Fwd: Re: CFT: vlc 2.0.8 (with two PRs applied)
Le 29/08/2013 20:27, Juergen Lock a écrit : > Hm that would mean vanilla radeon drivers are now broken for xv as > well, not good. :( Which card is this btw? > > I've Cc'd x11@ - maybe someone there has an idea... It's the same with the vesa driver in a VirtualBox VM. -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | * Trim your quotations. Really. Proudly powered by Open Source | Thank you :) signature.asc Description: OpenPGP digital signature
Re: Fwd: Re: CFT: vlc 2.0.8 (with two PRs applied)
Le 29/08/2013 20:08, Juergen Lock a écrit : >>> Is this using intel kms? radeon kms? Seems at least radeon kms doesn't >>> do xv with all cards yet, and vdpau even less so: >>> >>> https://wiki.freebsd.org/AMD_GPU >> >> I don't use any of them, but It's an ATI card. >> > Hmm maybe you are and don't know it? Nope, at all :) It’s impossible since my kernel conf is custom (GENERIC without drivers I don't use in fact) and don't include radeonkms drivers nor drm2. Then, these modules aren't loaded. The X.org drivers are those from the port tree and are not development ones that use KMS ;) -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | * Trim your quotations. Really. Proudly powered by Open Source | Thank you :) signature.asc Description: OpenPGP digital signature
Re: Fwd: Re: CFT: vlc 2.0.8 (with two PRs applied)
Le 29/08/2013 19:46, Juergen Lock a écrit : > On Thu, Aug 29, 2013 at 06:10:01PM +0200, Florent Peterschmitt wrote: >> Reading a video with new xorg, is not possible. The first "picture" is >> displayed and VLC hangs on. >> > Is this using intel kms? radeon kms? Seems at least radeon kms doesn't > do xv with all cards yet, and vdpau even less so: > > https://wiki.freebsd.org/AMD_GPU I don't use any of them, but It's an ATI card. However, I *can* read videos with these outputs: * SDL * X11 (XCB) It's the Xvideo output that makes VLC hanging, and Xvideo was chosen for the "predefined" output. Hum, do you know why VLC does choose this one by default? -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | * Trim your quotations. Really. Proudly powered by Open Source | Thank you :) signature.asc Description: OpenPGP digital signature
Fwd: Re: CFT: vlc 2.0.8 (with two PRs applied)
Message original Sujet: Re: CFT: vlc 2.0.8 (with two PRs applied) Date : Thu, 29 Aug 2013 18:08:20 +0200 De : Florent Peterschmitt Pour : freebsd-multime...@freebsd.org Le 29/08/2013 17:48, Gary Jennejohn a écrit : > Unluckily, the 2.0.7,3 port doesn't even compile, so I don't have > a working vlc anymore :( > > FreeBSD 10.0-CURRENT #10: Sat Aug 10 amd64 > VLC should build with the multimedia/vlc livemedia breakage patch. Try at least with it. I'll set up a 9.2-RC3 box to test VLC on it, maybe this night or tomorrow. -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | * Trim your quotations. Really. Proudly powered by Open Source | Thank you :) signature.asc Description: OpenPGP digital signature
Fwd: Re: CFT: vlc 2.0.8 (with two PRs applied)
Message original Sujet: Re: CFT: vlc 2.0.8 (with two PRs applied) Date : Wed, 28 Aug 2013 23:05:06 +0200 De : Florent Peterschmitt Pour : freebsd-multime...@freebsd.org Le 28/08/2013 22:26, Juergen Lock a écrit : > http://www.freebsd.org/cgi/query-pr.cgi?pr=181610 > livemedia breakage Builds fine :) I've got a problem with FreeBSD 10 (HEAD) and reading videos with it, for the moment I havn't much time to investigate by myself and since FreeBSD 10 should go into stable in few days, I'll fill a PR in due form if I'm not able to find any clue about the problem. If you or someone else is interested: Reading a video with new xorg, is not possible. The first "picture" is displayed and VLC hangs on. -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | * Trim your quotations. Really. Proudly powered by Open Source | Thank you :) signature.asc Description: OpenPGP digital signature
Re: Cacti vulnerable?
Le 28/08/2013 10:30, John Marino a écrit : > He is saying the ports tree version is 0.8.8a and thus not safe, the > response to the question "is the port tree version safe?" Aha, so I missed something :) > John -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | Thank you :) signature.asc Description: OpenPGP digital signature
Re: Cacti vulnerable?
Le 28/08/2013 10:10, Rodrigo OSORIO a écrit : > Hi, > > Not really, according to cve, releases before 0.8.8b are affected, > and we have 0.8.8a. > > - rodrigo And before 0.8.8b there is 0.8.8a. Or I missed something? -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | Thank you :) signature.asc Description: OpenPGP digital signature
Re: poudriere three pythons
Le 20/08/2013 17:27, Marko Cupać a écrit : > I am trying to set up local pkg repository, and am building packages > with poudriere. As a dependency for net/samba36 it builds python - not > only lang/python27 (like when built locally with portmaster), but: > > python-2.7.2-txz > python2-2.txz > python27-2.7.5_2.txz > > How to make it build just one python? Poudriere/pkgng don't prevent you to read UPDATING some times to be aware of changes in the port tree. -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | Thank you :) signature.asc Description: OpenPGP digital signature
Re: ★ Ports, Vincent left a message for you
Le 21/07/2013 02:04, Badoo a écrit : > […] > Have fun! > The Badoo Team AHAHAHA! Of course ports are sexy! signature.asc Description: OpenPGP digital signature
Re: Fwd: x11/kdelibs4 - rebuilding raptor2 needed ?
On 13.07.2013 15:56, Stan Gammons wrote: > Forgot to cc the list > > > >> From: Stan Gammons >> Date: July 13, 2013, 8:55:08 AM CDT >> To: Florent Peterschmitt >> Subject: Re: x11/kdelibs4 - rebuilding raptor2 needed ? >> >> Speaking of x11 and kde4. What is the "correct" way to build/install x11 and >> kde4? […] >> >> Stan Please send a new mail with a new subject to start a new discussion. Thanks. -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | * Answer to the list , not to me. | Thank you :) signature.asc Description: OpenPGP digital signature
x11/kdelibs4 - rebuilding raptor2 needed ?
From UPDATING 20130705, I did a portmaster -r kdelibs-4\* and it failed with "Could not find parser plugin for encoding trig *** [nepomuk/nie.h] Error code 1" on kdelibs port. After a little search, I found some saying to rebuild textproc/rasqal and textprocraptor. I've only rebuit raptor (texproc/raptor2 in fact) and the build is continuing, for the moment. Something missing in UPDATING ? -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | * Answer to the list (if so), not to me. | Thank you :) signature.asc Description: OpenPGP digital signature
Re: lang/php5 - separate apache module from php5 port
Le 10/07/2013 23:54, olli hauer a écrit : >> Here it would be ap22-mod_php5 and ap24-mod_php5. >> > > Thats what I thought with your first mail and I suspect this is a good idea. Yep, it was what I meant. So do you think I should contact the maintainer ? signature.asc Description: OpenPGP digital signature
Re: lang/php5 - separate apache module from php5 port
Le 10/07/2013 23:28, olli hauer a écrit : > Try APACHE_PORT=www/apache24 Ow… poudriere wants to rebuild everything… But, what if I want to keep both apache22 and apache24 in the repository ? A separate module would be useful. I have a question about that. Who to build two versions of one module ? Like for python, if I want py27 and py33 versions of the same module, under the same repository ? Here it would be ap22-mod_php5 and ap24-mod_php5. signature.asc Description: OpenPGP digital signature
Re: lang/php5 - separate apache module from php5 port
Le 10/07/2013 23:11, Loïc BLOT a écrit : > Hi, > if i understand you say php5 isn't usable with Apache2.4 ? > I'm using Apache 2.4 with PHP 5.4.16 without any problems on my devel > monitoring distro. > mod_perl have problems with Apache 2.4 but not php5 > Ah ? Have you defined DEFAULT_APACHE_VERSION=24 in make.conf ? Because I use poudriere and I haven't tried with. -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | Thank you :) signature.asc Description: OpenPGP digital signature
PHP5 - separate apache module from php5 port
Hi, Everything is in the title. Would it be possible to make a new port to build the apache (2.2) php module ? It will prevent php from not being installable with apache24 using this option. If help is needed, I can start working on it. But I never written any port :) -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | Thank you :) signature.asc Description: OpenPGP digital signature
lang/php5 - separate apache module from php5 port
Hi, Everything is in the title. Would it be possible to make a new port to build the apache (2.2) php module ? It will prevent php from not being installable with apache24 using this option. If help is needed, I can start working on it. But I never written any port :) -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | Thank you :) signature.asc Description: OpenPGP digital signature
Re: Rebuild all ports for perl minor version update?
Le 14/06/2013 10:12, Thomas Mueller a écrit : > I see in the $PORTSDIR/UPDATING file that perl has been updated. > > perl5.16 has been updated from 5.16.2 to 5.16.3 . > > Since this is only (?) a minor-version update, why should it be necessary to > upgrade all ports that depend on perl? > > portmaster -r perl > > In that case, why didn't they go to perl 5.18? > > Since so many ports depend on perl, and png too, maybe they should have > updated perl and png (to 1.6.x) at the same time, then two massive portmaster > or portupgrade runs could have been done together, as one even bigger > portmaster or portupgrade run? > > > Tom If you don't want to rebuild *really* everything depending on perl, you can first give a shot en perl modules: pkg info | sed -rn 's/^(p5.*)-[0-9]+.*/\1/p' | xargs portmaster Maybe this can be done using only pkg query but I'm too lazy for the moment 8-} But you should know that it can make other perl dependent ports not working anymore. -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | Thank you :) signature.asc Description: OpenPGP digital signature
Re: Can't build Xorg --> make failed for ports-mgmt/pkg
On 12.06.2013 13:52, Miguel Clara wrote: > I'm attempting to install kde4 in FreeBSD 10-current, after 3 days > dealing with some dependency issues I was able to install kde4 with > portmaster... > > Before kde already installed Xorg, but I get a "green" and sometime > "purple"screen when X starts, the log pointed me to this problem: > > http://www.mail-archive.com/freebsd-current@freebsd.org/msg146880.html > > However when trying to rebuild Xorg with portmaster it stops on "pkg" > with the following error: > > > --- pkg-static --- > gcc -O2 -pipe -I/usr/local/include -fno-strict-aliasing > -I/data/ports/ports-mgmt/pkg/work/pkg-1.0.12/pkg-static/../libpkg > -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall > -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual > -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align > -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls > -Wold-style-definition -Wno-pointer-sign -L/usr/local/lib -static -o > pkg-static add.o audit.o autoremove.o backup.o check.o clean.o > create.o delete.o event.o info.o install.o main.o progressmeter.o > query.o register.o repo.o rquery.o update.o upgrade.o search.o set.o > shlib.o updating.o utils.o version.o which.o fetch.o shell.o stats.o > -L/data/ports/ports-mgmt/pkg/work/pkg-1.0.12/pkg-static/../libpkg > -lpkg -larchive -lutil -lpthread -lsbuf -lfetch -lssl -lcrypto > -lmd -lz -lbz2 -llzma > -L/data/ports/ports-mgmt/pkg/work/pkg-1.0.12/pkg-static/../external/sqlite > -lbsdyml -lsqlite3 -larchive -lsbuf -lfetch -lpthread -lelf > -lssl -lcrypto -lmd -lz -lbz2 -llzma -ledit -lncursesw -ljail > /usr/local/lib/libpkg.a(pkgdb.o): In function `pkgdb_cmd': > pkgdb.c:(.text+0x947f): undefined reference to `sqlite3_shell' > *** [pkg-static] Error code 1 > > make: stopped in /data/ports/ports-mgmt/pkg/work/pkg-1.0.12/pkg-static > 1 error > = > > Is anyone else having this problem? Or has anyone build/installed > xorg+kde4 from ports on current with sucess? > > Thanks > ___ > 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" > First you should update your port tree, there is pkg 1.0.13. Are you building pkg on -CURRENT ? -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail. +33 (0)6 64 33 97 92 | * Send PDF for documents. http://florent.peterschmitt.fr | Thank you :) signature.asc Description: OpenPGP digital signature
VLC - latency at volume change
Hi, I've not found any bug report about that kind of problem and I prefer to send this both on -multimedia and -ports, because I don't know where the problem can be. It takes one to three seconds to VLC to change volume, it's a big latency. There was a similar bug in VLC's bugtracker for version 1.2, and is solved now. But maybe not in FreeBSD, after all it's maybe not the same code that manage "that". It's not the first time I see (mostly ear) that. I work on FreeBSD 9.1-STABLE r251605, snd_hda sound driver. -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail +33 (0)6 64 33 97 92 | * PDF for documents http://florent.peterschmitt.fr | Thank you :) signature.asc Description: OpenPGP digital signature
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
Le 07/06/2013 15:30, Tijl Coosemans a écrit : > On 2013-06-07 13:40, Baptiste Daroussin wrote: >> On Fri, Jun 07, 2013 at 12:46:08PM +0200, Tijl Coosemans wrote: >>> On 2013-06-07 12:17, Baptiste Daroussin wrote: >>>> On Fri, Jun 07, 2013 at 01:15:49PM +0300, Vitaly Magerya wrote: >>>>> Baptiste Daroussin wrote: >>>>>>> Is it possible to still show the dialog if one of those options implies >>>>>>> additional dependencies? >>>>>>> >>>>>>> If not, what should those of us who do not want them installed do? >>>>>> >>>>>> make config will always show those options so you can always tune them. >>>>>> >>>>>> just make config-conditional will not fireup a new dialog automatically >>>>>> if the >>>>>> defined options are only those from the global options. >>>>> >>>>> I see. As far as I can tell though, and correct me if I'm wrong, but >>>>> 'make install' doesn't show those options. It also does not show those >>>>> options for dependent ports. Neither does 'make config-recursive'. >>>>> >>>>> Tools like portmaster will now ignore those as well during install and >>>>> reinstall. >>>>> >>>>> So, again, what are my options if I don't want dependencies to be pulled >>>>> in silently? >>>> >>>> You have no options and you never had one in the ports tree sorry. >>>> >>>> If you have a way to implement that cleanly, I'll be happy to push such >>>> features >>>> in the ports but really I see a way to do what you ask for. >>> >>> How about only suppressing the dialog if the options have been explicitly >>> set or unset in make.conf? >> >> That would be easy but is that a really desired feature? > > I can only speak for myself, but I don't see DOCS as a global option. > For some ports I want documentation, for others I don't, so I want the > dialog to show up even if DOCS is the only option. > > There doesn't seem to be a clear cut line between global and per port > options and different users have different opinions about it. > > Can you make it such that config-conditional suppresses the dialog > if all options have been explicitly set or unset either through > command line, make.conf or optionsfile? Or in other words only show > the dialog if one of the options falls back to a default value (e.g. > when a new option has been added to a port and that option has not > been set globally). > > I think that would allow anyone to set/unset any option globally and > not be bothered by dialogs without enforcing that view on everybody > else. You wouldn't need GLOBAL_OPTIONS any more then. > Like you said, every users have different opinion (as I have another than yours :-) ) and the only way I think can satisfy every one is a customizable behavior… -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail +33 (0)6 64 33 97 92 | * PDF for documents http://florent.peterschmitt.fr | Thank you :) signature.asc Description: OpenPGP digital signature
Re: strange dialog4ports and xterm interaction
Le 06/06/2013 13:17, Michael Gmelin a écrit : > On Thu, 6 Jun 2013 13:00:49 +0200 > kalth...@googlemail.com wrote: > >> >> Hi, >> >> today I realized that when dialog4ports is running in xterm it isn't >> possible to scroll up or down (if you scrolled up before dialog4ports >> was executed) to previous or current output. Is it supposed to be >> that way? > > This only affects the mouse scrolling, this is due to dialog4ports > support mouse interaction (you can click items as well). You can still > scroll using shift+pgup/pgdown. > >> >> Regards, >> kaltheat Shouldn't dialog ignore mouse scrolling ? Is it possible to do so ? -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail +33 (0)6 64 33 97 92 | * PDF for documents http://florent.peterschmitt.fr | Thank you :) signature.asc Description: OpenPGP digital signature
Re: repo.txz not found
Le 06/06/2013 13:01, Raoul a écrit : > Hi all, > > Please, can you enlight me on this topic: > i run current: > > Updating repository catalogue > pkg: > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-current/All//repo.txz: > File unavailable (e.g., file not found, no access) > > thanks in advance > > rmgls > rm...@free.fr These repositories are in old pkg format, or at least, not the new one (pkgng). -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail +33 (0)6 64 33 97 92 | * PDF for documents http://florent.peterschmitt.fr | Thank you :) signature.asc Description: OpenPGP digital signature
Re: x11-toolkits/mx build fail
Le 26/05/2013 21:54, Lowell Gilbert a écrit : > Beeblebrox writes: > >> Sorry, my bad - port is part of marcuscom-gnome3 apparently. I have had so >> many port-build fails (consistently over a long period) that a neglected to >> check the port origin. >> Will report issue to marcuscom-gnome3 > > You have been issuing a *lot* of e-mails to the ports lists about > failure that do not occur in any other environment than yours. > > *Please* stop sending out such messages until you have fixed your own > environment. Just to support your comment. Beeblebrox: you're reporting many bugs without trying any fix by yourself, you don't care of others requests to start from a clean (from zero) environment. And over all, working on -CURRENT brings his lot of (possible) issues. You shouldn't use -CURRENT if you're not able by yourself to fix problems, at least trying to do something and stop losing your time and time of others reading error messages that doesn't makes sens. Again, it is *not* useful/usable to send error logs at every fail. -- Florent Peterschmitt | /"\ ASCII Ribbon Campaign flor...@peterschmitt.fr| \ / - No HTML/RTF in E-mail +33 (0)6 64 33 97 92 | X - No proprietary attachments http://florent.peterschmitt.fr | / \ - Respect for open standards signature.asc Description: OpenPGP digital signature
Re: Proposal: do not show up the dialog(1) by default?
Le 23/05/2013 08:36, Xin Li a écrit : > On 5/22/13 10:45 PM, Baptiste Daroussin wrote: >> hi, > >> A lot of people seems to be complaining about the configuration >> dialog popping up all the time. > >> What if we change the default behaviour to not pop up the dialog >> each time there is a changed option but only when the user >> explicitly type make config? > >> Just a proposal, please give your opinion. > >> Of course make config-recursive behaviour won't change. > > I think this would be a good idea. If the a majority of users need to > change default options, then the default should be changed. > > Not really related to the dialog, but maybe, I mean maybe, we can > teach package tools to just go ahead download and install package, if > the options being chosen matches the package options, if the host > system meets certain criteria (e.g. is a supported release or > -CURRENT) and the package is available? > > Another idea is to collect the options from user, and send it as a > feedback (the user have reviewed the default and either accepted it, > or have changed). This would help port maintainers to decide which > options should be made default, etc. What you're thinking about is a sort of intelligent dialog ? In my opinion, dialog should *not* pop-up and take options like this: * A default option changed by user has changed -> take user's one * All default options unchanged by user-> take new defaults And we should let user the choice of the behavior. Also give an automated feedback to default options is not a bad idea. > Cheers, -- Florent Peterschmitt | /"\ ASCII Ribbon Campaign flor...@peterschmitt.fr| \ / - No HTML/RTF in E-mail +33 (0)6 64 33 97 92 | X - No proprietary attachments http://florent.peterschmitt.fr | / \ - Respect for open standards signature.asc Description: OpenPGP digital signature
Re: teTeX and TeXLive
Le 11/05/2013 20:36, Hiroki Sato a écrit : > Hello, > > As you already noticed, TeXLive ports have been imported and one can > choose teTeX or TeXLive while the default value for pre-compiled > packages is still teTeX. > > If you want to use TeXLive, please try to use the following knob: > > TEX_DEFAULT= texlive > > To do this, almost all of ports which use TeX will depend on TeXLive. > Although some ports which install a new TeX macro package may not > work because of incompatibility such as difference of directory > structure between the two, ones which use TeX for typesetting should > work fine. Ones to install macro packages which were non-standard in > teTeX but are included in TeXLive will be fixed or removed. > > Please test TeXLive and send your failure report to me. Once it is > confirmed that TEX_DEFAULT=texlive works, I will switch the default > value from tetex to texlive at some point. > > -- Hiroki > Oh really nice, thanks a lot ! -- Florent Peterschmitt +33 (0)6 64 33 97 92 flor...@peterschmitt.fr O< ascii ribbon campaign - stop html mail - www.asciiribbon.org signature.asc Description: OpenPGP digital signature
Re: devel/imake build breaks
Le 10/05/2013 19:45, Beeblebrox a écrit : > Workaround / solution here: > http://freebsd.1045724.n5.nabble.com/devel-imake-build-breaks-td5810289.html > > > > - > 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 & > xorg.devel > > -- > View this message in context: > http://freebsd.1045724.n5.nabble.com/devel-imake-build-breaks-tp5809186p5810301.html > Sent from the freebsd-ports mailing list archive at Nabble.com. > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > Why didn't you tried to do this first ? And: "Since gcpp is a preprocessor, you can try to simlink gcpp (in /usr/local/bin of course) to a valid c++ preprocessor." - me. Ok I wasn't as clear as "Niclas Zeising-6"… -- Florent Peterschmitt +33 (0)6 64 33 97 92 flor...@peterschmitt.fr O< ascii ribbon campaign - stop html mail - www.asciiribbon.org signature.asc Description: OpenPGP digital signature
Re: mail/postfix - automated install : bypass default mailer message
Le 10/05/2013 04:04, Sahil Tandon a écrit : > On Thu, 2013-05-09 at 18:08:55 +0200, Florent Peterschmitt wrote: > >> In pkg-install.in it's said if POSTFIX_DEFAULT_MTA=YES then postfix will >> be set as default mailer in /etc/mail/mailer.conf >> >> So, I do export POSTFIX_DEFAULT_MTA=YES but the only thing it does is >> setting the default answer to yes. > > Correct. > >> So is it possible to make the installation fully automated, without any >> ask ? > > Set BATCH=yes. > Oh I though it was only useful for port building (don't ask for options). Thanks -- Florent Peterschmitt +33 (0)6 64 33 97 92 flor...@peterschmitt.fr O< ascii ribbon campaign - stop html mail - www.asciiribbon.org signature.asc Description: OpenPGP digital signature
mail/postfix - automated install : bypass default mailer message
Hi,
In pkg-install.in it's said if POSTFIX_DEFAULT_MTA=YES then postfix will
be set as default mailer in /etc/mail/mailer.conf
So, I do export POSTFIX_DEFAULT_MTA=YES but the only thing it does is
setting the default answer to yes.
So is it possible to make the installation fully automated, without any
ask ?
Should we do yes | pkg install postfix ?
I think it should be possible to have a non-interactive installation,
via an environment variable.
This *should* work:
--- pkg-install.in 2013-05-09 18:01:41.802404861 +0200
+++ pkg-install.in 2013-05-09 18:06:04.858404947 +0200
@@ -83,7 +83,13 @@
egrep -q "^newaliases.*${PREFIX}/sbin/sendmail" ${MC}
ret=$?
if [ ${ret} -ne 0 ]; then
- if yesno "Would you like to activate Postfix in ${MC}"
${DEFAULT_REPLACE_MAILERCONF}; then
+ local postfix_ret
+ if [ -z ${POSTFIX_DEFAULT_MTA_FORCE} ]; then
+ postfix_ret=$(yesno "Would you like to activate
Postfix in ${MC}" ${DEFAULT_REPLACE_MAILERCONF})
+ else
+ postfix_ret=0
+ fi
+ if ${postfix_ret}; then
/bin/mv -f ${MC} ${MC}.old
echo "#"
> ${MC}
echo -n "# Execute the Postfix sendmail program"
>> ${MC}
--
Florent Peterschmitt
+33 (0)6 64 33 97 92
flor...@peterschmitt.fr
O< ascii ribbon campaign
- stop html mail
- www.asciiribbon.org
signature.asc
Description: OpenPGP digital signature
Re: print/tex-aleph: web2c.h:28: error: expected '=', ',', '; ', 'asm' or '__attribute__' before '*' token
How did you « start from scratch » ? Deleting all port tree and options related to *tex* or selectively removed each part of texlive ? Le 08/05/2013 16:09, Anton Shterenlikht a écrit : > I tried to remove all texlive related ports and start > from scratch. Now I have this error: > > cc -DHAVE_CONFIG_H -I. -I./kpathsea -I./../.. -Wimplicit -Wreturn-type > -Wdeclaration-after-statemnt -Wno-unknown-pragmas -O2 -pipe > -I/usr/local/include -fno-strict-aliasing -MT kps.o -MD -MP -MF .eps/kps.Tpo > -c -o kps.o kps.c && mv -f .deps/kps.Tpo .deps/kps.Po > In file included from kps.c:26: > web2c.h:28: error: expected '=', ',', ';', 'asm' or '__attribute__' before > '*' token > web2c.h:43: error: expected specifier-qualifier-list before 'boolean' > web2c.h:58: warning: parameter names (without types) in function declaration > web2c.h:63: warning: parameter names (without types) in function declaration > web2c.h:64: warning: parameter names (without types) in function declaration > web2c.h:65: warning: parameter names (without types) in function declaration > kps.c:33: error: expected '=', ',', ';', 'asm' or '__attribute__' before > 'uppercasify' > kps.c:52: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' > token > kps.c:70: error: expected ')' before '*' token > cc -DHAVE_CONFIG_H -I. -I./kpathsea -I./../.. -Wimplicit -Wreturn-type > -Wdeclaration-after-statemnt -Wno-unknown-pragmas -O2 -pipe > -I/usr/local/include -fno-strict-aliasing -MT fixwrites.o -MD -MP-MF > .deps/fixwrites.Tpo -c -o fixwrites.o fixwrites.c && mv -f > .deps/fixwrites.Tpo .deps/fixwrites.o > gmake[3]: *** [kps.o] Error 1 > gmake[3]: Leaving directory > `/usr/ports/print/tex-aleph/work/texlive-20120701-source/texk/web2c/webc' > gmake[2]: *** [web2c/stamp-splitup] Error 2 > gmake[2]: *** Waiting for unfinished jobs > cc -DHAVE_CONFIG_H -I. -I./kpathsea -I./../.. -Wimplicit -Wreturn-type > -Wdeclaration-after-statemnt -Wno-unknown-pragmas -O2 -pipe > -I/usr/local/include -fno-strict-aliasing -MT kps.o -MD -MP -MF .eps/kps.Tpo > -c -o kps.o kps.c && mv -f .deps/kps.Tpo .deps/kps.Po > /bin/sh ./libtool --tag=CC --mode=link cc -Wimplicit -Wreturn-type > -Wdeclaration-after-statement Wno-unknown-pragmas -O2 -pipe > -I/usr/local/include -fno-strict-aliasing -o fixwrites fixwrites.o ps.o > libtool: link: cc -Wimplicit -Wreturn-type -Wdeclaration-after-statement > -Wno-unknown-pragmas -O2 -ipe -I/usr/local/include -fno-strict-aliasing -o > fixwrites fixwrites.o kps.o > echo timestamp >stamp-fixwrites > gmake[3]: Leaving directory > `/usr/ports/print/tex-aleph/work/texlive-20120701-source/texk/web2c/webc' > touch web2c/stamp-fixwrites > gmake[2]: Leaving directory > `/usr/ports/print/tex-aleph/work/texlive-20120701-source/texk/web2c' > gmake[1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory > `/usr/ports/print/tex-aleph/work/texlive-20120701-source/texk/web2c' > gmake: *** [all] Error 2 > *** [do-build] Error code 1 > > Stop in /usr/ports/print/tex-aleph. > > This is on ia64 r247266 with ports at r317640. > > Let me know if you prefer that I open a PR for this. > > Thank you > > Anton > > ___ > 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" > -- Florent Peterschmitt +33 (0)6 64 33 97 92 flor...@peterschmitt.fr O< ascii ribbon campaign - stop html mail - www.asciiribbon.org signature.asc Description: OpenPGP digital signature
Re: devel/imake build breaks
Le 06/05/2013 20:41, Beeblebrox a écrit :
> Nope - unfortunately gcp is "gnu cp", which I have on my system due to
> requirements for linux-based source building.
>
> none of these work-around attempts in /etc/make.conf work:
> Solution 1:
> CC=gcc46
> CXX=g++46
> CPP=cpp46
>
> Solution 2:
> CC:=${CC:C,^gcc46,/usr/local/libexec/ccache/world/gcc46,1}
> CXX:=${CXX:C,^g\+\+\46,/usr/local/libexec/ccache/world/g++46,1}
>
> soultion 3:
> USE_GCC=any
>
> The c-preprocessors we can use are /usr/bin/clang-cpp OR /usr/bin/cpp -
> which target you prefer to create the link to?
Hum. I can't help you anymore now. You should ask why it uses gcpp
(first time ever I see this) and you could try to patch the port to make
it use the right preprocessor, then submit it ;)
--
Florent Peterschmitt
+33 (0)6 64 33 97 92
flor...@peterschmitt.fr
O< ascii ribbon campaign
- stop html mail
- www.asciiribbon.org
signature.asc
Description: OpenPGP digital signature
Re: devel/imake build breaks
Le 06/05/2013 19:37, Beeblebrox a écrit : > /usr/local/bin has a file name gcp - that's the pre-processor AFAIK. So this? > > # ln -s /usr/local/bin/gcp /usr/local/bin/gcpp > # ln -s /usr/local/bin/gcp /usr/bin/gcpp > > gcp ? huh. Try a man (no a men, a $ man gcp) or pkg query %Fp gcc | grep gcp at firts. -- Florent Peterschmitt +33 (0)6 64 33 97 92 flor...@peterschmitt.fr O< ascii ribbon campaign - stop html mail - www.asciiribbon.org signature.asc Description: OpenPGP digital signature
Re: devel/imake build breaks
Le 06/05/2013 19:18, Beeblebrox a écrit : > Hi - I apparently mis-read your message as "ports tree" "instead of "source > tree". No problem :) > # pkg query %?Fp gcc | grep gcpp -> pkg: No match > > /etc/src.conf has these entries: > WITH_CLANG_EXTRAS= yes > WITH_CLANG_IS_CC= yes > WITH_LIBCPLUSPLUS= yes > WITHOUT_GCC=yes > Since gcpp is a preprocessor, you can try to simlink gcpp (in /usr/local/bin of course) to a valid c++ preprocessor. -- Florent Peterschmitt +33 (0)6 64 33 97 92 flor...@peterschmitt.fr O< ascii ribbon campaign - stop html mail - www.asciiribbon.org signature.asc Description: OpenPGP digital signature
Re: devel/imake build breaks
Le 06/05/2013 19:04, Beeblebrox a écrit : > # pkg info gcc > gcc-4.6.3 GNU Compiler Collection 4.6 > > Please see: > http://freebsd.1045724.n5.nabble.com/compiler-confusion-gcc-cannot-be-located-and-causes-compiler-errors-td5797633.html#a5797872 > What about pkg query %?Fp gcc | grep gcpp ? -- Florent Peterschmitt +33 (0)6 64 33 97 92 flor...@peterschmitt.fr O< ascii ribbon campaign - stop html mail - www.asciiribbon.org signature.asc Description: OpenPGP digital signature
Re: devel/imake build breaks
Le 06/05/2013 18:57, Beeblebrox a écrit : > Error message is: > > checking if cc supports -Werror=attributes... yes > checking how to run the C preprocessor... cpp > checking for cpp... (cached) gcpp > checking if gcpp requires -undef... ./configure: gcpp: not found > ./configure: gcpp: not found > ./configure: gcpp: not found > configure: error: gcpp defines unix with or without -undef. I don't know > what to do. > ===> Script "configure" failed unexpectedly. > Please report the problem to x...@freebsd.org [maintainer] and attach the > "/asp/obj/asp/git/ports/devel/imake/work/imake-1.0.5/config.log" including > the output of the failure of your make command. Also, it might be a good > idea > to provide an overview of all packages installed on your system (e.g. a > /usr/local/sbin/pkg info -g -Ea). > *** [do-configure] Error code 1 > > Stop in /asp/git/ports/devel/imake. > Sounds like you hav'nt gcpp in your system. Since you run FreeBSD 10, look at this util in the source tree, build and install it if exists. > > > - > 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 & > xorg.devel > > -- > View this message in context: > http://freebsd.1045724.n5.nabble.com/devel-imake-build-breaks-tp5809186.html > Sent from the freebsd-ports mailing list archive at Nabble.com. > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > -- Florent Peterschmitt +33 (0)6 64 33 97 92 flor...@peterschmitt.fr O< ascii ribbon campaign - stop html mail - www.asciiribbon.org signature.asc Description: OpenPGP digital signature
Re: poudriere - postgresql90-client, LDAP, requires ldap.h
Le 28/04/2013 08:05, Scot Hetzel a écrit :
> On Sat, Apr 27, 2013 at 4:32 PM, Florent Peterschmitt <
> flor...@peterschmitt.fr> wrote:
>
>> Le 27/04/2013 23:13, Matthew Seaman a écrit :
>>> On 27/04/2013 19:49, Florent Peterschmitt wrote:
>>>> Hello,
>>>>
>>>> I use the latest poudriere-devel to make my own pkg repository, and
>>>> would like to build postgresql with LDAP support.
>>>>
>>>> Since it's in a virgin jail, and because the log said « hey I need
>>>> ldap.h », I understand that openldap should be installed but, is it the
>>>> good way to do ? For each package requirement, it is needed to install
>>>> it by hand ? (or with previously built packages :) )
>>>>
>>>
>>> You should use the 'poudriere options' command to enable LDAP support in
>>> the postgresql server.
>>
>> Yep, I did that. Sorry, I missed to say I already have done this. The
>> problem is that when building the package, the configure step fail
>> saying ldap.h is missing.
>>
>>> Now, when you use poudriere to build the postgresql package, it will
>>> have LDAP client added as a requirement -- so poudriere will also build
>>> you an LDAP package -- and when you go to install postgresql, ldap will
>>> be installed as well as a dependency.
>>>
>>> Cheers,
>>>
>>> Matthew
>>>
>> Yep. But how does work poudriere ? Because I have built postfix and
>> dovecot2 with LDAP support and there was no problem. I think it's a
>> problem from the port itself and not from poudriere, I should try in a
>> new system (perhaps, a jail, without poudriere).
>>
>
> The problem seems to be caused by the following from
> databases/postgresql91-server/Makefile:
>
> 66 .if !defined(CLIENT_ONLY) && !defined(SLAVE_ONLY)
> 67 SERVER_ONLY= yes
> 68 USE_RC_SUBR= postgresql
> 69 USE_PGSQL= yes
> 70 WANT_PGSQL_VER=
> ${DISTVERSION:C/([0-9][0-9]*)\.([0-9][0-9]*).*/\1\2/g}
> 71 USERS= ${PG_USER}
> 72 GROUPS= ${PG_GROUP}
> 73 SUB_FILES+= 502.pgsql
> 74 .endif
>
> 81 .if !defined(SLAVE_ONLY)
> 82 OPTIONS_DEFINE+= NLS DTRACE PAM LDAP GSSAPI OPTIMIZED_CFLAGS XML
> TZDATA DEBUG KRB5
> 83 OPTIONS_SINGLE= KRB5
> 84 OPTIONS_SINGLE_KRB5= MIT_KRB5 HEIMDAL_KRB5
> :
> 112 OPTIONS_DEFAULT= NLS XML TZDATA INTDATE SSL
> 113 .endif # !SLAVE_ONLY
>
> 159 . if ${PORT_OPTIONS:MLDAP}
> 160 CONFIGURE_ARGS+=--with-ldap
> 161 . if defined (SERVER_ONLY)
> 162 USE_OPENLDAP= yes
> 163 . endif
> 164 . endif
>
> NOTE: postgresql90-client/Makefile includes postgresql90-server/Makefile
> which then includes postgresql91-server/Makefile
>
> Unfortunately, you can't set USE_OPENLDAP as a build depends. Try
> commenting out lines 161 and 163 in the postgresql91-server/Makefile. This
> will add OpenLDAP as a LIB_DEPENDS to the postgresql*-client ports.
>
> Scot
>
Ah ok so it's not a problem from poudriere :) So I'll do that and retry
soon, thanks.
--
Florent Peterschmitt
+33 (0)6 64 33 97 92
flor...@peterschmitt.fr
O< ascii ribbon campaign
- stop html mail
- www.asciiribbon.org
signature.asc
Description: OpenPGP digital signature
Re: poudriere - postgresql90-client, LDAP, requires ldap.h
Le 27/04/2013 23:13, Matthew Seaman a écrit : > On 27/04/2013 19:49, Florent Peterschmitt wrote: >> Hello, >> >> I use the latest poudriere-devel to make my own pkg repository, and >> would like to build postgresql with LDAP support. >> >> Since it's in a virgin jail, and because the log said « hey I need >> ldap.h », I understand that openldap should be installed but, is it the >> good way to do ? For each package requirement, it is needed to install >> it by hand ? (or with previously built packages :) ) >> > > You should use the 'poudriere options' command to enable LDAP support in > the postgresql server. Yep, I did that. Sorry, I missed to say I already have done this. The problem is that when building the package, the configure step fail saying ldap.h is missing. > Now, when you use poudriere to build the postgresql package, it will > have LDAP client added as a requirement -- so poudriere will also build > you an LDAP package -- and when you go to install postgresql, ldap will > be installed as well as a dependency. > > Cheers, > > Matthew > Yep. But how does work poudriere ? Because I have built postfix and dovecot2 with LDAP support and there was no problem. I think it's a problem from the port itself and not from poudriere, I should try in a new system (perhaps, a jail, without poudriere). -- Florent Peterschmitt +33 (0)6 64 33 97 92 flor...@peterschmitt.fr O< ascii ribbon campaign - stop html mail - www.asciiribbon.org signature.asc Description: OpenPGP digital signature
poudriere - postgresql90-client, LDAP, requires ldap.h
Hello, I use the latest poudriere-devel to make my own pkg repository, and would like to build postgresql with LDAP support. Since it's in a virgin jail, and because the log said « hey I need ldap.h », I understand that openldap should be installed but, is it the good way to do ? For each package requirement, it is needed to install it by hand ? (or with previously built packages :) ) -- Florent Peterschmitt +33 (0)6 64 33 97 92 flor...@peterschmitt.fr O< ascii ribbon campaign - stop html mail - www.asciiribbon.org signature.asc Description: OpenPGP digital signature
Re: Change design of py-* ruby-* ports
On 25/04/2013 22:03, David Demelier wrote:
> Hello,
>
> Currently the ports tree has unified ports for python and ruby modules with
> origin like databases/py-sqlalchemy. When someone wants to bulk the ports
> tree
> to create packages the databases/py-sqlalchemy will only be built against the
> current python version set in Mk/bsd.python.mk (or overriden in make.conf).
>
> This is a very bad design and we should fix that as soon as possible, we are
> a
> lot of people and some portmgr folks included that is not the best way to
> manage python / ruby modules.
>
> Let say I want to install a package, unfortunately this one requires some
> python modules that are only working for python 2.7 but me as a developer I
> want to develop with python 3, then we are stuck.
>
> What we need to do now, is to move *all* py-* and ruby-* to their respective
> versions i.e py27-* and ruby19 (or 18?).
>
> Then we will need to copy all of these and set them to the newer version so
> py33 and ruby20.
>
> Also this will remove the breakage of OPTIONS, all of these ports needs the
> dirty hack of OPTIONSFILE because of the ${PKGNAMEPREFIX}.
>
> This will blow out the ports tree by adding a lot of ports, but it's the best
> way to cover the both version and future bulk generation for users.
>
> Regards,
>
I agree with you. I thought about a PYTHON_VERSION="27 33" variable in
/etc/make.conf, generating each version of the module for each python
version if the port is able to do it, but then you may build versions of
module you don't need.
But before (don't know when), it was like you say. py27-, py26, and
everything merged to py-
I was not as implied as now in FreeBSD project but it was surelly
motivated by something.
--
Florent Peterschmitt
+33 (0)6 64 33 97 92
flor...@peterschmitt.fr
O< ascii ribbon campaign
- stop html mail
- www.asciiribbon.org
signature.asc
Description: OpenPGP digital signature
Re: Port lang/python33 does not build
Le 25/04/2013 04:23, Kubilay Kocak a écrit : > On 24/04/2013 11:18 PM, Florent Peterschmitt wrote: >> The same here. Default options, no CFLAGS tunning, up-to-date ports, >> sams system. >> >> Le 24/04/2013 14:40, Tzanetos Balitsaris a écrit : >>> Hello, >>> >>> The port lang/python33 cannot be built. It stops when it tries to >>> compile the module posixmodule.c >>> >>> cc -DNDEBUG -O2 -pipe -fno-strict-aliasing -O2 -pipe >>> -fno-strict-aliasing -O2 -pipe -fno-strict-aliasing -I. >>> -I./../Include -fPIC -DPy_BUILD_CORE -c ./../Modules/posixmodule.c -o >>> Modules/posixmodule.o >>> ./../Modules/posixmodule.c: In function 'posix_waitid': >>> ./../Modules/posixmodule.c:6883: error: 'idtype_t' undeclared (first use >>> in this function) >>> ./../Modules/posixmodule.c:6883: error: (Each undeclared identifier is >>> reported only once >>> ./../Modules/posixmodule.c:6883: error: for each function it appears in.) >>> ./../Modules/posixmodule.c:6883: error: expected ';' before 'idtype' >>> ./../Modules/posixmodule.c:6888: error: 'idtype' undeclared (first use >>> in this function) >>> ./../Modules/posixmodule.c: In function 'all_ins': >>> ./../Modules/posixmodule.c:11497: error: 'P_PID' undeclared (first use >>> in this function) >>> ./../Modules/posixmodule.c:11498: error: 'P_PGID' undeclared (first use >>> in this function) >>> ./../Modules/posixmodule.c:11499: error: 'P_ALL' undeclared (first use >>> in this function) >>> *** [Modules/posixmodule.o] Error code 1 >>> >>> Stop in /usr/ports/lang/python33/work/Python-3.3.0/portbld.shared. >>> *** [pre-build] Error code 1 >>> >>> Stop in /usr/ports/lang/python33. >>> *** [build] Error code 1 >>> >>> Stop in /usr/ports/lang/python33. >>> >>> This happens on a FreeBSD 9.1-RELEASE GENERIC amd64 system. >>> >>> >>> This message was sent using IMP, the Internet Messaging Program. >>> >>> >>> ___ >>> 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" >> >> > > Investigated and turned out it was related to the config.site changes > that were committed recently. This overrode what ./configure would have > otherwise found, namely that waitpid was not available. > > waitpid(2) is not in 9.1-RELEASE, but is in stable/9 onward. > > A fix has been committed: http://svnweb.freebsd.org/changeset/ports/316493 > > Please update your ports trees and try the build again. > > Thank you nox for making the link, and bdrewery for taking care of it so > quickly. > > -- > Ta, > > Koobs Build and install OK. Do you have any python script to test if it really works ? signature.asc Description: OpenPGP digital signature
Re: Port lang/python33 does not build
The same here. Default options, no CFLAGS tunning, up-to-date ports, sams system. Le 24/04/2013 14:40, Tzanetos Balitsaris a écrit : > Hello, > > The port lang/python33 cannot be built. It stops when it tries to > compile the module posixmodule.c > > cc -DNDEBUG -O2 -pipe -fno-strict-aliasing -O2 -pipe > -fno-strict-aliasing -O2 -pipe -fno-strict-aliasing -I. > -I./../Include -fPIC -DPy_BUILD_CORE -c ./../Modules/posixmodule.c -o > Modules/posixmodule.o > ./../Modules/posixmodule.c: In function 'posix_waitid': > ./../Modules/posixmodule.c:6883: error: 'idtype_t' undeclared (first use > in this function) > ./../Modules/posixmodule.c:6883: error: (Each undeclared identifier is > reported only once > ./../Modules/posixmodule.c:6883: error: for each function it appears in.) > ./../Modules/posixmodule.c:6883: error: expected ';' before 'idtype' > ./../Modules/posixmodule.c:6888: error: 'idtype' undeclared (first use > in this function) > ./../Modules/posixmodule.c: In function 'all_ins': > ./../Modules/posixmodule.c:11497: error: 'P_PID' undeclared (first use > in this function) > ./../Modules/posixmodule.c:11498: error: 'P_PGID' undeclared (first use > in this function) > ./../Modules/posixmodule.c:11499: error: 'P_ALL' undeclared (first use > in this function) > *** [Modules/posixmodule.o] Error code 1 > > Stop in /usr/ports/lang/python33/work/Python-3.3.0/portbld.shared. > *** [pre-build] Error code 1 > > Stop in /usr/ports/lang/python33. > *** [build] Error code 1 > > Stop in /usr/ports/lang/python33. > > This happens on a FreeBSD 9.1-RELEASE GENERIC amd64 system. > > > This message was sent using IMP, the Internet Messaging Program. > > > ___ > 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" signature.asc Description: OpenPGP digital signature
Re: Growing list of required(ish) ports
Le mardi 09 avril 2013 à 13:03 -0400, Robert Simmons a écrit : > > Hum, I didn't thought about that. So I think it would be possible to > > have a secondary « branch » for the distribution including something > > like « special ports » which can be retrieved, built and managed (for > > porters) quickly. > > > > Anybody think something like that is relevant and possible to do ? > > One thing to note is that these parts of base are kept just about as > up-to-date as ports over in the HEAD branch. In the case of OpenSSH, > HEAD is way way more up to date than ports. These changes are also > fairly quickly MFC'd over to stable. The real hiccup is that these > changes don't dribble out of freebsd-update. I see. So you suggest to use -STABLE ? Because -RELEASE is aimed to stay as frozen (I mean stable and secured) as possible, it makes sens not to have updates. -- Florent Peterschmitt +33 (0)6 64 33 97 92 flor...@peterschmitt.fr signature.asc Description: This is a digitally signed message part
Re: Growing list of required(ish) ports
Le mardi 09 avril 2013 à 06:09 -0700, Darren Pilgrim a écrit : > On 2013-04-08 10:22, Florent Peterschmitt wrote: > > Yep, OpenSSH is tiny enought to keep it in base system. It would be a > > big loss not to have it by default, securely installed in the base > > system. > > I really wish it wasn't. Having OpenSSH (and thus OpenSSL) in the base > means FreeBSD has an outdated version installed by default. You have to > install openssl from ports in order to have modern cipher support, TLS > v1.1/1.2, DTLS, etc. This puts two sets of openssl libs on the system > and creates recurrent headaches with builds where the autoconfiguration > selects the wrong set of libs. Hum, I didn't thought about that. So I think it would be possible to have a secondary « branch » for the distribution including something like « special ports » which can be retrieved, built and managed (for porters) quickly. Anybody think something like that is relevant and possible to do ? -- Florent Peterschmitt +33 (0)6 64 33 97 92 flor...@peterschmitt.fr signature.asc Description: This is a digitally signed message part
Re: Growing list of required(ish) ports
Le lundi 08 avril 2013 à 17:40 +0200, Daniel Nebdal a écrit : > On Mon, Apr 8, 2013 at 5:26 PM, Freddie Cash wrote: > > Note: I may have messed up the quoting/attribution by snipping things. > > > > On Sun, Apr 7, 2013 at 10:11 PM, Kevin Oberman wrote: > > > >> On Sun, Apr 7, 2013 at 8:34 PM, Kimmo Paasiala wrote: > >> > >> > > On the other hand, there are a number of things that I think should be > >> > > pulled out of base. Some already have ports, and others would need > >> > > ports created. Examples of things to pull out of base are OpenSSL, > >> > > Heimdal, OpenSSH, PF, ntpd, ipfilter, bind, sendmail, and others. > >> > > Code that is typically way behind the upstream project basically. > >> > > > >> > > >> > I think Bryan already explained the reasons why pkg should not be in > >> > base, it's an external tool that is not strictly required to get a bare > >> > bones FreeBSD system up and running. Including it in base you create > >> > yet another maintainance burden and would slow down the development of > >> > the ports/packages management tools. > >> > >> What people seem to miss is that putting tools into the base system > >> strangles the tools. Look at the difficulty we have seen in updating > >> openssl. perl was removed from base for exactly that reason. Once something > >> is in base, it usually can only be updated on major releases and even then > >> it can be very complicated. That is a problem for any dynamically changing > >> tool. > >> > >> I would love to see BIND removed from base, but most of the things you > >> listed really are hard to remove. I know that I don't want to try bringing > >> up a new install of FreeBSD on a remote system without OpenSSH and that > >> pulls in openssl. In the case of many tools, it really turns into a > >> bikeshed. But i can see no reason to add any of the new packaging tools > >> simply because it is critical that updates be possible far more often than > >> is possible for the base system. > >> > >> Moving OpenSSH, OpenSSL, etc into the ports tree, but making the pkgs > > available on the installation media, and having a final hook at the end to > > install "required" pkgs, would solve that. There's already a "do you want > > to enable OpenSSH daemon" question in the installed, so adding "pkg add > > /path/to/openssh-x.y.z.txz" wouldn't be hard. > > > > Same for bind, sendmail, kerberos, etc. For instance, just add a "daemon > > selection screen" for each bit removed from base, to select which ones you > > want installed as part of the OS install. > > > > The hard part comes in finding stub/clients for each item moved to a pkg, > > such that a desktop-oriented install is not hampered (ie, SSH client is > > usable, DNS lookups can be done, local mail can be generated/delivered, > > etc). > > > > The really hard part is coming up with a migration path for those who > > upgrade via source builds. > > -- > > Freddie Cash > > fjwc...@gmail.com > > > There's also the issue that OpenSSH is used for remote administration > - being able to do destructive things with pkg without worrying about > continued SSH-access is rather relaxing. With danger of entering > bikeshed territory, it's one of the things that makes FreeBSD more > relaxing than the Linuxes: You can blast every installed package and > still be fine - and a working sshd is a part of "fine" for me, since > it's kind of a requirement for doing anything else. > > Admittedly, my personal worst-case scenario is "drag a monitor and > keyboard to the other side of the room", so I will probably survive > either way. :) > > -- > Daniel Nebdal Yep, OpenSSH is tiny enought to keep it in base system. It would be a big loss not to have it by default, securely installed in the base system. > ___ > 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" -- Florent Peterschmitt +33 (0)6 64 33 97 92 flor...@peterschmitt.fr signature.asc Description: This is a digitally signed message part
Re: Ports should provide knobs disabling unwanted network services
Le 26/03/2013 10:00, Peter Pentchev a écrit : > On Tue, Mar 26, 2013 at 09:13:38AM +0100, Florent Peterschmitt wrote: >> Le 25/03/2013 04:40, Scot Hetzel a écrit : >>> On Sun, Mar 24, 2013 at 10:33 PM, Florent Peterschmitt >>> wrote: >>>> Le 24/03/2013 17:34, Scot Hetzel a écrit : >>>>> On Sun, Mar 24, 2013 at 7:00 AM, Beeblebrox wrote: >>>>>> I would be very happy to submit a patch, if I actually knew how to write >>>>>> one... >>>>>> >>>>> >>>>> It is quite simple to create the patch. >>>>> >>>>> If you have a working copy checked out with svn, then it would be: >>>>> >>>>> cd /usr/ports/[category]/[port] >>>>> - Make the necessary changes to the port >>>>> - After testing the port make sure to do a 'make clean' >>>>> svn diff > port.diff >>>>> >>>>> Otherwise make a copy of the port: >>>>> >>>>> cd /usr/ports/[catagory] >>>>> cp port port-orig >>>>> cd port >>>>> - Make the necessary changes to port >>>>> - After testing port make sure to do a 'make clean' >>>>> cd .. >>>>> diff -ruN port-orig port > port.diff >>>>> >>>>> Then just submit the port.diff in a PR using either send-pr or >>>>> http://www.freebsd.org/send-pr.html. >>>>> >>>> >>>> Is there a way to manually make a patch that will say : >>>> >>>> --- MyFile >>>> +++ MyFile >>>> >>>> Even if these files are in two distinct trees ? >>>> >>> There is always a way to do that: >>> >>> diff -u /path/to/original/port/MyFile /path/to/modified/port/MyFile > >>> /place/to/save/patch/port.diff >>> >>> or if you modifed several files: >>> >>> diff -ruN /path/to/original/port /path/to/modified/port > >>> /place/to/save/patch/port.diff >>> >> Hum yes but what I mean is that we'll have, for example: >> >> --- /home/florent-gentoo/patch/old/one 2013-03-24 14:04:20.757200724 >> +0100 >> +++ /home/florent-gentoo/patch/new/one 2013-03-24 14:04:08.541201548 >> +0100 >> […] >> >> And what I want is: >> >> --- /home/florent-gentoo/patch/old/one 2013-03-24 14:04:20.757200724 >> +0100 >> +++ /home/florent-gentoo/patch/old/one 2013-03-24 14:04:08.541201548 >> +0100 >> […] >> >> SCM make patches like the second one and I'm no sure it is possible to >> do without modifying by hand the patch generated. > > Well, one way to do it would be to actually *use* an SCM :) My > preferred way would be a Git copy of the Subversion repository - then > you do your changes in your local Git tree and periodically pull down > the changes from the FreeBSD Subversion repo and merge them into yours. > > But really, is there actually a reason why you don't want two separate > directories? To be honest, before the advent of Subversion and Git > everyone did their patches that way (well, there *were* local CVS > repositories and checkouts from there, but most of the patches were > diffs between two side-by-side directories) - and I don't think anyone > ever complained. Are there any problems you are seeing with two paths > in the diff headers, or is it just aesthetic? > > G'luck, > Peter > Hum. I'm definitively misunderstanding patching process and I just discovered that even if the header is not with the two same subdirs, it works anyway. For the moment I've no time for porting but I'll study it as soon as possible :) Thanks ;) -- Florent Peterschmitt +33 (0)6 64 33 97 92 flor...@peterschmitt.fr signature.asc Description: OpenPGP digital signature
Re: Ports should provide knobs disabling unwanted network services
Le 25/03/2013 04:40, Scot Hetzel a écrit : > On Sun, Mar 24, 2013 at 10:33 PM, Florent Peterschmitt > wrote: >> Le 24/03/2013 17:34, Scot Hetzel a écrit : >>> On Sun, Mar 24, 2013 at 7:00 AM, Beeblebrox wrote: >>>> I would be very happy to submit a patch, if I actually knew how to write >>>> one... >>>> >>> >>> It is quite simple to create the patch. >>> >>> If you have a working copy checked out with svn, then it would be: >>> >>> cd /usr/ports/[category]/[port] >>> - Make the necessary changes to the port >>> - After testing the port make sure to do a 'make clean' >>> svn diff > port.diff >>> >>> Otherwise make a copy of the port: >>> >>> cd /usr/ports/[catagory] >>> cp port port-orig >>> cd port >>> - Make the necessary changes to port >>> - After testing port make sure to do a 'make clean' >>> cd .. >>> diff -ruN port-orig port > port.diff >>> >>> Then just submit the port.diff in a PR using either send-pr or >>> http://www.freebsd.org/send-pr.html. >>> >> >> Is there a way to manually make a patch that will say : >> >> --- MyFile >> +++ MyFile >> >> Even if these files are in two distinct trees ? >> > There is always a way to do that: > > diff -u /path/to/original/port/MyFile /path/to/modified/port/MyFile > > /place/to/save/patch/port.diff > > or if you modifed several files: > > diff -ruN /path/to/original/port /path/to/modified/port > > /place/to/save/patch/port.diff > Hum yes but what I mean is that we'll have, for example: --- /home/florent-gentoo/patch/old/one 2013-03-24 14:04:20.757200724 +0100 +++ /home/florent-gentoo/patch/new/one 2013-03-24 14:04:08.541201548 +0100 […] And what I want is: --- /home/florent-gentoo/patch/old/one 2013-03-24 14:04:20.757200724 +0100 +++ /home/florent-gentoo/patch/old/one 2013-03-24 14:04:08.541201548 +0100 […] SCM make patches like the second one and I'm no sure it is possible to do without modifying by hand the patch generated. -- Florent Peterschmitt +33 (0)6 64 33 97 92 flor...@peterschmitt.fr signature.asc Description: OpenPGP digital signature
Re: Ports should provide knobs disabling unwanted network services
Le 24/03/2013 17:34, Scot Hetzel a écrit : > On Sun, Mar 24, 2013 at 7:00 AM, Beeblebrox wrote: >> I would be very happy to submit a patch, if I actually knew how to write >> one... >> > > It is quite simple to create the patch. > > If you have a working copy checked out with svn, then it would be: > > cd /usr/ports/[category]/[port] > - Make the necessary changes to the port > - After testing the port make sure to do a 'make clean' > svn diff > port.diff > > Otherwise make a copy of the port: > > cd /usr/ports/[catagory] > cp port port-orig > cd port > - Make the necessary changes to port > - After testing port make sure to do a 'make clean' > cd .. > diff -ruN port-orig port > port.diff > > Then just submit the port.diff in a PR using either send-pr or > http://www.freebsd.org/send-pr.html. > Is there a way to manually make a patch that will say : --- MyFile +++ MyFile Even if these files are in two distinct trees ? -- Florent Peterschmitt +33 (0)6 64 33 97 92 flor...@peterschmitt.fr signature.asc Description: OpenPGP digital signature
Re: Ports should provide knobs disabling unwanted network services
It's no something difficult. Rewrite the Makefile port (based on the one already here of course) and use diff util. Or if you want, submit the whole file ;) Le 24/03/2013 12:00, Beeblebrox a écrit : > I would be very happy to submit a patch, if I actually knew how to write > one... > > > > -- > View this message in context: > http://freebsd.1045724.n5.nabble.com/Ports-should-provide-knobs-disabling-unwanted-network-services-tp5798581p5798594.html > Sent from the freebsd-ports mailing list archive at Nabble.com. > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > -- Florent Peterschmitt +33 (0)6 64 33 97 92 flor...@peterschmitt.fr signature.asc Description: OpenPGP digital signature
Re: Ports should provide knobs disabling unwanted network services
If you want, you can submit a little patch adding choice to disable these options. You'll see if it is adopted or not, but you have more chance to get your request done with something than without. Le 24/03/2013 11:09, Beeblebrox a écrit : > Many ports, (specially the KDE-related ones) provide no option to disable > network-related options. Usually these are things like samba-client, > Avahi-mDNS* (with variants), and the like. Gnome usually provides a choice > to disable gnome-vfs. > > I really don't understand why such ports enable those services by default, > then provide a warning along the lines of "if you are unhappy with the > security risk present through this service, uninstall the port... etc." > > I usually end up hacking the Makefile and disabling the cr*p that I don't > want, then build. I understand the purpose of those services, but as an > example, is net/mDNSResponder REALLY mandatory for everyone who intends to > use graphics/okular? > > > > > -- > View this message in context: > http://freebsd.1045724.n5.nabble.com/Ports-should-provide-knobs-disabling-unwanted-network-services-tp5798581.html > Sent from the freebsd-ports mailing list archive at Nabble.com. > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > -- Florent Peterschmitt +33 (0)6 64 33 97 92 flor...@peterschmitt.fr signature.asc Description: OpenPGP digital signature
Re: www/firefox: crashing when intend to play video/streaming
Le 20/03/2013 07:00, Chris Rees a écrit : > On 19 Mar 2013 19:04, "O. Hartmann" wrote: >> >> On Tue, 2013-03-19 at 23:30 +0900, Jan Beich wrote: >>> "O. Hartmann" writes: >>> >>>> When trying to play a video from YouTube or any other type of stream > on >>>> a website providing it, Firefox is "crashing" >>> >>> ARIFF_OSS option/patch in audio/alsa-plugins is not really maintained >>> and probably only needed for 7.x which is now EOL. It has a known >>> issue (see ports/170473) where www/firefox built with ALSA would >>> crash unless you set media.use_cubeb -> false in about:config. >>> >>> If you don't use youtube.com/html5 then my guess would be an issue >>> with IPC e.g., libevent14 is getting in the way again. Try setting >>> dom.ipc.plugins.enabled -> false. >> >> Hello. >> >> Thanks for this hint! >> I deactivated ALSA in the opetions-menu (as well as RTC stuff since it >> only builds with ALSA). I used PULSEAUDIO instead. I also configured the >> option in Firefox itself as recommended. The result is, that now the >> videos, no matter how they are embedded in a webpage, can be played >> again and Firefox isn't crashing anymore. dom.ipc.plugins.enabled -> >> true also remains the Firefox stable. > > Why not try the OSS option? Pulseaudio is usually a waste of time. > > Chris Yep, I've OSS for firefox and it works fine. PA is for dependency purpose, isn't it ? > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > -- Florent Peterschmitt +33 (0)6 64 33 97 92 flor...@peterschmitt.fr signature.asc Description: OpenPGP digital signature
Re: www/firefox: crashing when intend to play video/streaming
Have you custom CFLAGS ? I often encountered many problems with custom CFLAGS and it is really not very useful. Other thing, did you try to build it with system GCC ? Le 19/03/2013 07:18, O. Hartmann a écrit : > Port www/firefox is crashing since a couple of months for now when used > on FreeBSD 9.1-STABLE and FreeBSD 10.0-CURRENT (both most recent > sources, compiled with CLANG, port www/firefox also compiled with > CLANG). > > Before digging deeper I'd like to exclude a special issue with my setup. > > When trying to play a video from YouTube or any other type of stream on > a website providing it, Firefox is "crashing", no, the better term would > be "closing", since there is no error message on the system. Firefox > (most recent version, but this happened also with the previous three or > four versions) is simply closing. Even when forcing Firefox to ask to > close tabs, it doesn't ask. This seems to be strange. > > So my question is does anybody else have encountered such a behaviour? > > Please CC me, I do not subscribe this list. > > Thanks in advance, > > Oliver > > signature.asc Description: OpenPGP digital signature
Re: How can I switch compiler from clang to gcc46?
If you put these environment variables into make.conf ? Le 16/03/2013 13:53, Beeblebrox a écrit : > I changed env as proposed, to full path (path is correct, btw) > CC=/usr/local/bin/gcc46 > CXX=/usr/local/bin/g++46 > CPP=/usr/local/bin/cpp46 > I also placed same in the Makefile of 3rd party source. > >> you need to .. persuade your Makefile to run a different compiler. > That's exactly what I want to do, but I'm not getting there. > Any other ideas? Should I start tearing down $PATH? > > > > -- > View this message in context: > http://freebsd.1045724.n5.nabble.com/How-can-I-switch-compiler-from-clang-to-gcc46-tp5796040p5796052.html > Sent from the freebsd-ports mailing list archive at Nabble.com. > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > signature.asc Description: OpenPGP digital signature
Re: fail2ban install issue
Le 13/03/2013 13:35, Olivier Smedts a écrit : > 2013/3/13 Florent Peterschmitt : >> I just test, it works well. Maybe the problem was solved the time for >> you to write this email :) > ...or ftp.freebsd.org is an out-of-date mirror. > > The fetch append on github and failed on it: "Attempting to fetch https://github.com/fail2ban/fail2ban/tarball/0.8.8/fail2ban-fail2ban-0.8.8-0-g51a3be2.tar.gzInitializing download: https://github.com/fail2ban/fail2ban/tarball/0.8.8/fail2ban-fail2ban-0.8.8-0-g51a3be2.tar.gzToo many redirects." And so ftp.freebsd.org is not synced too. signature.asc Description: OpenPGP digital signature
Re: fail2ban install issue
I just test, it works well. Maybe the problem was solved the time for you to write this email :) Le 12/03/2013 22:21, Donald Wheeler a écrit : > Hi, > I have read good things about fail2ban, and I would love to install it! > I am sorry to trouble you if I am doing something dumb. > My server is freebsd-9.1-release, I've updated my ports tree. > I get this error when I go to install from ports: > root@jupiter:/usr/ports/security/py-fail2ban # uname -aFreeBSD > jupiter.my.domain 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243826: Tue Dec 4 > 06:55:39 UTC 2012 > r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > i386root@jupiter:/usr/ports/security/py-fail2ban # make install clean===> > License GPLv2 accepted by the user===> py27-fail2ban-0.8.8_1 depends on > file: /usr/local/sbin/pkg - found=> fail2ban-fail2ban-0.8.8-0-g51a3be2.tar.gz > doesn't seem to exist in /usr/ports/distfiles/.=> Attempting to fetch > https://github.com/fail2ban/fail2ban/tarball/0.8.8/fail2ban-fail2ban-0.8.8-0-g51a3be2.tar.gzInitializing > download: > https://github.com/fail2ban/fail2ban/tarball/0.8.8/fail2ban-fail2ban-0.8.8-0-g51a3be2.tar.gzToo > many redirects. > => Attempting to fetch > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/fail2ban-fail2ban-0.8.8-0-g51a3be2.tar.gzInitializing > download: > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/fail2ban-fail2ban-0.8.8-0-g51a3be2.tar.gzFile > not found. > => Couldn't fetch it - please try to retrieve this=> port manually into > /usr/ports/distfiles/ and try again.*** [do-fetch] Error code 1 > Stop in > /usr/ports/security/py-fail2ban.root@jupiter:/usr/ports/security/py-fail2ban # > If you could point me in the right direction, I would be grateful! > Regards,Don Wheeler > ___ > 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" > signature.asc Description: OpenPGP digital signature
Re: Why portlint require MASTER_SITE to end with /?
I tried with
http://gitorious.org/mdb/mdb/archive-tarball/6dab37f2acaef70a31f65bd485fdc2648d2b
for example, where 6dab37f2acaef70a31f65bd485fdc2648d2b is the
commit "hash".
The file retrived was
mdb-mdb-6dab37f2acaef70a31f65bd485fdc2648d2b.tar.gz
Is that you want ?
Le 11/03/2013 19:05, Xin Li a écrit :
> Hi,
>
> While working on a project hosted at gitorious, I end up with
> something like this:
>
> MASTER_SITES=
> https://gitorious.org/${GO_ACCOUNT}/${GO_PROJECT}/archive-tarball/${GO_TAGNAME}?dummy=
> [...]
> GO_ACCOUNT= mdb
> GO_PROJECT= mdb
> GO_TAGNAME= ${PORTNAME:U}_${PORTVERSION:S/./_/g}
> FETCH_ARGS?= -o - > ${DISTDIR}/${DISTFILES}
>
> However, portlint gives the following warning, which I think is wrong:
>
> FATAL: Makefile: URL
> "https://gitorious.org/${GO_ACCOUNT}/${GO_PROJECT}/archive-tarball/${GO_TAGNAME}?dummy=";
> should end with "/" or a group name (e.g. :something).
>
> Can this be made a non-fatal one, or do we have better way to handle
> gitorious source packages?
>
> 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"
>
signature.asc
Description: OpenPGP digital signature
Re: libxdg-basedir-1.2.0.tar.gz unavailable
Le 11/03/2013 18:51, John Marino a écrit : > On 3/11/2013 20:43, Florent Peterschmitt wrote: >> Hello, >> >> I'm a user of x11-wm/awesome and on a fresh install, I can't build it >> because libxdg-basedir-1.2.0 sources are not available. >> >> But I found a tarball from OpenBSD distfiles that worked out of the box >> after fetched in /usr/ports/distfiles directory. >> >> Here is the link : >> http://ftp.fr.openbsd.org/pub/OpenBSD/distfiles//libxdg-basedir-1.2.0.tar.gz >> >> >> If someone could import it on FreeBSD's disfiles repos, I think it would >> not be bad :) >> > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/176779 > > A good resource to check first... > John > Woops, totally I've forgotten that. ___ > 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" signature.asc Description: OpenPGP digital signature
libxdg-basedir-1.2.0.tar.gz unavailable
Hello, I'm a user of x11-wm/awesome and on a fresh install, I can't build it because libxdg-basedir-1.2.0 sources are not available. But I found a tarball from OpenBSD distfiles that worked out of the box after fetched in /usr/ports/distfiles directory. Here is the link : http://ftp.fr.openbsd.org/pub/OpenBSD/distfiles//libxdg-basedir-1.2.0.tar.gz If someone could import it on FreeBSD's disfiles repos, I think it would not be bad :) signature.asc Description: OpenPGP digital signature
Re: x11/Terminal - why not xfce4-terminal
Le 26/09/2012 14:10, Olivier Duchateau a écrit : 2012/9/26 Florent Peterschmitt: Le 26/09/2012 12:26, Sergey V. Dyatko a écrit : On Wed, 26 Sep 2012 14:17:57 + Florent Peterschmitt wrote: Hello, Why the terminal emulator from XFCE4 is called Terminal instead of xfce4-terminal ? http://goodies.xfce.org/projects/applications/terminal Ok, then next question. Why xfce apps are not under un sub-directory called xfce (or xfce4 if versionning becomes important) ? What do you mean by « Why xfce apps are not under un sub-directory called xfce » ? Have something like /usr/ports/xfce/ ? ___ 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/Terminal - why not xfce4-terminal
Le 26/09/2012 12:26, Sergey V. Dyatko a écrit : On Wed, 26 Sep 2012 14:17:57 + Florent Peterschmitt wrote: Hello, Why the terminal emulator from XFCE4 is called Terminal instead of xfce4-terminal ? http://goodies.xfce.org/projects/applications/terminal Ok, then next question. Why xfce apps are not under un sub-directory called xfce (or xfce4 if versionning becomes important) ? ___ 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/Terminal - why not xfce4-terminal
Hello, Why the terminal emulator from XFCE4 is called Terminal instead of xfce4-terminal ? ___ 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 system "problems"
On 26.06.2012 17:21, Jeremy Messenger wrote: On Tue, Jun 26, 2012 at 3:44 AM, Baptiste Daroussin wrote: On Tue, Jun 26, 2012 at 10:34:00AM +0200, Marcus von Appen wrote: Matthew Seaman: On 26/06/2012 08:26, Marcus von Appen wrote: 1. Ports are not modular What do you mean by modular? if you are speaking about subpackages it is coming, but it takes time I hope, we are not talking about some Debian-like approach here (foo-bin, foo-dev, foo-doc, ). Actually, yes -- that's pretty much exactly what we're talking about here. Why do you feel subpackages would be a bad thing? Because it makes installing ports more complex, causes maintainers to rip upstream installation routines apart, and burdens users with additional tasks to perform for what particular benefit (except saving some disk space)? If I want to do some development the Debian way, I would need to do the following: - install foo-bin (if it ships with binaries) - install foo-lib (libraries, etc.) - install foo-dev (headers, etc.) - install foo-doc (API docs) With the ports I am currently doing: - install foo I agree. yes but you do not allow to install 2 packages one depending on mysql51 and one depending on mysql55, there will be conflicts on dependency just because of developpement files, the runtime can be made not to conflict. I trust maintainers to no abuse package splitting and do it when it make sense. In the case you give I would probably split the package that way: foo (everything needed in runtime: bin + libraries) foo-dev (everything needed for developper: headers, static libraries, pkg-config stuff, libtool stuff, API docs) foo-docs (all user documentation about the runtime) of course there will be no rule on how to split packages, just common sense. Disagree. We shouldn't split for that. Have you seen how many Linux users report when they can't compile one of application, just because they didn't install the *-dev? A LOT (thousands and thousands)! When it's A LOT then it means that it's flawed. If the upstream provide the split tarballs then I do not have any problem with it. Also, it will slow down the ports tree pretty bad if we do that way to all ports. regards, Bapt Just don't make -dev package, that's really something stupid and I agree with that. ___ 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 system "problems"
On 26.06.2012 11:03, Matthew Seaman wrote:
On 26/06/2012 09:17, Andrea Venturoli wrote:
On 06/26/12 09:58, Matthew Seaman wrote:
On 26/06/2012 08:26, Marcus von Appen wrote:
1. Ports are not modular
What do you mean by modular? if you are speaking about subpackages it
is coming,
but it takes time
I hope, we are not talking about some Debian-like approach here
(foo-bin,
foo-dev, foo-doc, ).
Actually, yes -- that's pretty much exactly what we're talking about
here. Why do you feel subpackages would be a bad thing?
Can I share my 2c?
Because it will just multiply be three the number of ports each of us
has to install/maintain/upgrade/etc...
Yes, it will multiply the number of ports. By three is about right,
given that most ports will only have port-docs and port-examples
sub-ports. However, first of all, you are assuming that the effort
required to install each of those sub-ports is the same as it is to
install a single port now. That is simply not the case.
If you want to install the foo/bar port, then (as now) you'ld
essentially[+] --
# cd ${PORTSDIR}/foo/bar
# make
# make install
but you'ld end up with bar-0.99, bar-doc-0.99 and bar-examples-0.99
installed. Unless you have a setting like NOPORTDOCS or NOPORTEXAMPLES
(probably controlled by a dialogue menu like any other options) which
means you don't get the associated -docs or -examples sub-ports.
That's no real change in terms of what you'ld have to do compared to now.
The difference is that if you install from packages, you now have the
opportunity not to install docs or examples.
Secondly, that's just one example of how sub-ports should work, and
docs/examples will be special-cased given their ubiquity. Most
sub-ports would be controlled by port OPTIONS dialogues.
A typical example would involve client-server apps -- so mysqlNN-server
becomes a sub-port of mysqlNN-client. You get to check a box saying
'install the server as well as the client' when you go to install
mysqlNN. Similarly all those php5-XYZ modules become sub-ports of
lang/php5. The big difference being that the port and all its sub-ports
are compiled in one step, and just packaged separately. Which is
probably less work overall that the current situation with ports and
slave-ports.
Cheers,
Matthew
[+] Or more likely you'ld use portupgrade or portmaster or similar to
run these steps for you.
Hello,
It's exactly what I wanted to say. I think so that port system should
adapt to this way of building ports. I mean that is instead of having
vala, we have vala-bin, vala-doc, vala-lib and vala-examples, and port
system don't untar vala archive for each port, but once and pick up
files into this unique directory. Then no waste of time because untar is
what takes most time for big ports.
We should still have a vala port, which is used to configure what we
want (other subports -examples, -lib and -doc).
But where it can be very useful, it's when we have a big port made of
many libraries, like Mono. We should be able to split it, because I
don't want to build everything.
For the GNOME question, if an option in the GNOME configuration port
says "[x] Yelp, will break help menus if not set", then no problem,
don't you think ?
___
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"
Port system "problems"
Hello, I'm not a developer and I know how it's difficult to make a port (or some ports, for example VirtualBox) but I think the port system has many "problems": 1. Ports are not modular 2. Option system is not really well documented 3. Some dependencies are totally useless 4. So slow... Let me give some examples: 1. games/wesnoth should be splitted in games/wesnoth-bin and games/wesnoth-datas. Why rebuild everything when just binaries needs ? 2. Why do we have to put WITH_NEW_XORG in /etc/make.conf to get it ? Why not put this var in a port configuration file which will be read by all ports needing this var ? 3. Why does GNOME really needs x11/yelp which depends on www/libxul, which is a big port to build ? I don't need yelp and I'm sure not to be alone don't need this. 4. Generating Index, find dependencies. I know that we have time and that's not a priority, but it is slow. I know that FreeBSD doesn't "change" because of "less surprising" philosophy (and I'm the first to say it's a good thing, but sometimes not so good), and also *BSD community is certainly less big than GNU community... Port system will have some major updates in the future ? ___ 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: print/ghostscript9 build fail : vga.h not found
On 24.06.2012 02:46, Hiroki Sato wrote: Florent Peterschmitt wrote in <4fe1b98b.5040...@gmail.com>: fp> gmake: *** [so] Erreur 2 fp> *** Error code 1 fp> fp> Stop in /usr/ports/print/ghostscript9. fp> *** Error code 1 fp> fp> Stop in /usr/ports/print/ghostscript9. fp> fp> Problem : no vga.h in my system, even in source tree. print/ghostscript9 depends on graphics/svgalib which provides vga.h. Please check if svgalib is installed properly. -- Hiroki graphics/svgalib is installed, but even after deinstall and reinstall, no vga.h and vgagl.h. Manual copy from work build directory of svgalib to /usr/local/include of these two files makes print/ghostscript9 build. Should I submit a PR to svgalib ? ___ 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"
print/ghostscript9 build fail : vga.h not found
sudo make MAKE_ARGS= cc -DHAVE_MKSTEMP -DHAVE_FONTCONFIG -DHAVE_LIBIDN -DHAVE_SETLOCALE -DHAVE_SSE2 -DHAVE_DBUS -O2 -pipe -fno-strict-aliasing -fPIC -DUPD_SIGNAL=0 -I. -I/usr/ports/print/ghostscript9/work/ghostscript-9.05/lcms/include -I/usr/local/include/libpng -I/usr/ports/print/ghostscript9/work/ghostscript-9.05/openjpeg/libopenjpeg -I/usr/ports/print/ghostscript9/work/ghostscript-9.05/openjpeg -I/usr/local/include -Wall -Wstrict-prototypes -Wundef -Wmissing-declarations -Wmissing-prototypes -Wwrite-strings -Wno-strict-aliasing -Wdeclaration-after-statement -fno-builtin -fno-common -DHAVE_STDINT_H=1 -DHAVE_SYS_TIME_H=1 -DGX_COLOR_INDEX_TYPE="unsigned long int" -O2 -pipe -fno-strict-aliasing -DUSE_LIBICONV_GNU -DUSE_LIBPAPER -I/usr/local/include -DGS_DEVS_SHARED -DGS_DEVS_SHARED_DIR=\"/usr/local/lib/ghostscript/9.05\" -fPIC -I./soobj -I./base -DWHICH_CMS="lcms2" -o ./soobj/gdevl256.o -c ./base/gdevl256.c ./base/gdevl256.c:33:17: error: vga.h: No such file or directory ./base/gdevl256.c:34:19: error: vgagl.h: No such file or directory ./base/gdevl256.c: In function 'lvga256_open': ./base/gdevl256.c:104: warning: implicit declaration of function 'vga_init' ./base/gdevl256.c:105: warning: implicit declaration of function 'vga_getdefaultmode' ./base/gdevl256.c:107: error: 'G320x200x256' undeclared (first use in this function) ./base/gdevl256.c:107: error: (Each undeclared identifier is reported only once ./base/gdevl256.c:107: error: for each function it appears in.) ./base/gdevl256.c:108: warning: implicit declaration of function 'vga_setmode' ./base/gdevl256.c:109: warning: implicit declaration of function 'gl_setcontextvga' ./base/gdevl256.c:110: warning: implicit declaration of function 'vga_getxdim' ./base/gdevl256.c:111: warning: implicit declaration of function 'vga_getydim' ./base/gdevl256.c:122: warning: implicit declaration of function 'gl_setpalettecolor' ./base/gdevl256.c: In function 'lvga256_close': ./base/gdevl256.c:136: error: 'TEXT' undeclared (first use in this function) ./base/gdevl256.c: In function 'lvga256_map_rgb_color': ./base/gdevl256.c:150: warning: ISO C90 forbids mixed declarations and code ./base/gdevl256.c: In function 'lvga256_copy_mono': ./base/gdevl256.c:227: warning: implicit declaration of function 'gl_fillbox' ./base/gdevl256.c:238: warning: implicit declaration of function 'gl_setpixel' ./base/gdevl256.c: In function 'lvga256_copy_color': ./base/gdevl256.c:261: warning: implicit declaration of function 'gl_putbox' ./base/gdevl256.c: In function 'lvga256_draw_line': ./base/gdevl256.c:301: warning: implicit declaration of function 'gl_line' gmake[2]: *** [soobj/gdevl256.o] Erreur 1 gmake[2]: *** Attente des tâches non terminées gmake[2] : on quitte le répertoire « /usr/ports/print/ghostscript9/work/ghostscript-9.05 » gmake[1]: *** [so-subtarget] Erreur 2 gmake[1] : on quitte le répertoire « /usr/ports/print/ghostscript9/work/ghostscript-9.05 » gmake: *** [so] Erreur 2 *** Error code 1 Stop in /usr/ports/print/ghostscript9. *** Error code 1 Stop in /usr/ports/print/ghostscript9. Problem : no vga.h in my system, even in source tree. ___ 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"
Vala 0.17.1 - Makefile and pkg-plist
Hi,
Here are the makefile and pkg-plist for vala 0.17.1 :
# New ports collection makefile for:vala
# Date created:2007-07-09
# Whom:Michael Johnson
#
# $FreeBSD: ports/lang/vala/Makefile,v 1.29 2011/11/09 15:25:37 miwi Exp $
# $MCom: ports/lang/vala/Makefile,v 1.55 2011/06/02 12:10:13 kwm Exp $
#
PORTNAME=vala
PORTVERSION=0.17.1
CATEGORIES=lang gnome
MASTER_SITES=GNOME
MAINTAINER=gn...@freebsd.org
COMMENT=Programming language and compiler that converts Vala code
into C code
LICENSE=LGPL21
LICENSE_FILE=${WRKSRC}/COPYING
USE_XZ=yes
USE_GNOME=gnomehack glib20 gnomeprefix libxslt
GNU_CONFIGURE=yes
USE_GETTEXT=yes
CPPFLAGS+=-I${LOCALBASE}
LDFLAGS+=-L${LOCALBASE}/lib
USE_BISON=build
USE_LDCONFIG=yes
MAN1?=valac.1 valac-0.18.1
PLIST_SUB=VERSION=0.18
.include
.if defined(VALA_SLAVE)
LIB_DEPENDS+=vala-0.17.1:${PORTSDIR}/lang/vala
CONFIGURE_ARGS+=--enable-vapigen
BUILD_DEPENDS+=
${SITE_PERL}/${PERL_ARCH}/XML/LibXML.pm:${PORTSDIR}/textproc/p5-XML-LibXML
RUN_DEPENDS+=
${SITE_PERL}/${PERL_ARCH}/XML/LibXML.pm:${PORTSDIR}/textproc/p5-XML-LibXML
MAN1=vala-gen-introspect.1 vapigen.1
.else
CONFIGURE_ARGS+=--disable-vapigen
.endif
post-patch:
# We cheat here, because vala records vapigen related stuff in its .pc file
# This makes the vapigen work again, although it might get weird when
# vala-vapigen isn't installed.
@${REINPLACE_CMD} -e
's|@vapigen_decl@|vapigen=$${bindir}/vapigen-0.17|g' \
-e
's|@gen_introspect_decl@|gen_introspect=$${libdir}/vala-0.17/gen-introspect-0.17|g'
\
-e
's|@vala_gen_introspect_decl@|vala_gen_introspect=$${bindir}/vala-gen-introspect-0.17|g'
\
${WRKSRC}/libvala.pc.in
@${REINPLACE_CMD} -e 's|cp $$< $$@|cp libvala.pc libvala-0.18.pc|g' \
${WRKSRC}/Makefile.in
.if defined(VALA_SLAVE)
pre-build:
@cd ${WRKSRC} && ${GMAKE} version.h
@cd ${WRKSRC}/gobject-introspection && ${GMAKE} libgidl.la && \
${GMAKE} gen-introspect
post-install:
@cd ${WRKSRC}/gobject-introspection && ${GMAKE} install
@${INSTALL_MAN} ${WRKSRC}/doc/vapigen.1
${WRKSRC}/doc/vala-gen-introspect.1 \
${PREFIX}/man/man1/
.else
# want to see what will fail.
post-install:
${LN} -fs ${PREFIX}/libdata/pkgconfig/libvala-0.18.pc \
${PREFIX}/libdata/pkgconfig/vala-1.0.pc
.endif
.include
bin/vala
bin/vala-0.18
bin/valac
bin/valac-0.18
include/vala-0.18/vala.h
include/vala-0.18/valaccode.h
include/vala-0.18/valacodegen.h
include/vala-0.18/valagee.h
lib/libvala-0.18.la
lib/libvala-0.18.so
lib/libvala-0.18.so.0
libdata/pkgconfig/libvala-0.18.pc
libdata/pkgconfig/vala-1.0.pc
man/man1/valac-0.18.1.gz
man/man1/valac.1.gz
share/aclocal/vala.m4
share/devhelp/books/vala-0.18/attributes.html
share/devhelp/books/vala-0.18/classes.html
share/devhelp/books/vala-0.18/default.css
share/devhelp/books/vala-0.18/delegates.html
share/devhelp/books/vala-0.18/enums.html
share/devhelp/books/vala-0.18/exceptions.html
share/devhelp/books/vala-0.18/expressions.html
share/devhelp/books/vala-0.18/index.html
share/devhelp/books/vala-0.18/interfaces.html
share/devhelp/books/vala-0.18/methods.html
share/devhelp/books/vala-0.18/namespaces.html
share/devhelp/books/vala-0.18/overview.html
share/devhelp/books/vala-0.18/statements.html
share/devhelp/books/vala-0.18/structs.html
share/devhelp/books/vala-0.18/types.html
share/devhelp/books/vala-0.18/vala-0.18.devhelp2
share/licenses/vala-0.17.1/LGPL21
share/licenses/vala-0.17.1/LICENSE
share/licenses/vala-0.17.1/catalog.mk
share/vala-0.18/vapi/alsa.deps
share/vala-0.18/vapi/alsa.vapi
share/vala-0.18/vapi/atk.vapi
share/vala-0.18/vapi/avahi-client.vapi
share/vala-0.18/vapi/avahi-gobject.deps
share/vala-0.18/vapi/avahi-gobject.vapi
share/vala-0.18/vapi/bzlib.vapi
share/vala-0.18/vapi/cairo-xcb.deps
share/vala-0.18/vapi/cairo-xcb.vapi
share/vala-0.18/vapi/cairo.vapi
share/vala-0.18/vapi/ccss-1.vapi
share/vala-0.18/vapi/clutter-1.0.deps
share/vala-0.18/vapi/clutter-1.0.vapi
share/vala-0.18/vapi/clutter-gst-1.0.deps
share/vala-0.18/vapi/clutter-gst-1.0.vapi
share/vala-0.18/vapi/clutter-gtk-0.10.deps
share/vala-0.18/vapi/clutter-gtk-0.10.vapi
share/vala-0.18/vapi/clutter-gtk-1.0.deps
share/vala-0.18/vapi/clutter-gtk-1.0.vapi
share/vala-0.18/vapi/clutter-json-1.0.vapi
share/vala-0.18/vapi/cogl-1.0.deps
share/vala-0.18/vapi/cogl-1.0.vapi
share/vala-0.18/vapi/cogl-pango-1.0.deps
share/vala-0.18/vapi/cogl-pango-1.0.vapi
share/vala-0.18/vapi/curses.vapi
share/vala-0.18/vapi/dbus-glib-1.vapi
share/vala-0.18/vapi/enchant.vapi
share/vala-0.18/vapi/fuse.deps
share/vala-0.18/vapi/fuse.vapi
share/vala-0.18/vapi/gconf-2.0.vapi
share/vala-0.18/vapi/gdk-2.0.deps
share/vala-0.18/vapi/gdk-2.0.vapi
share/vala-0.18/vapi/gdk-3.0.deps
share/vala-0.18/vapi/gdk-3.0.vapi
share/vala-0.18/vapi/gdk-pixbuf-2.0.deps
share/vala-0.18/vapi/gdk-pixbuf-2.0.vapi
share/vala-0.18/vapi/gdk-x11-2.0.deps
share/vala-0.18/vapi/gdk-x11-2.0.v
