Re: HEADS UP --- Update to x11-toolkits/fltk coming
Hi *, now I'm testing x11-toolkits/fltk for math/octave port. sorry for delay. thanks From: Pietro Cerutti g...@freebsd.org Subject: Re: HEADS UP --- Update to x11-toolkits/fltk coming Date: Tue, 06 Sep 2011 15:53:31 +0200 On 2011-Sep-06, 08:28, Stephen Montgomery-Smith wrote: On 09/06/2011 07:32 AM, Pietro Cerutti wrote: On 2011-Sep-06, 07:28, Stephen Montgomery-Smith wrote: On 09/06/2011 06:26 AM, Stephen Montgomery-Smith wrote: On 09/06/2011 04:18 AM, Pietro Cerutti wrote: Hi, you're receiving this email because one of your ports depends on x11-toolkits/fltk, according to $ grep fltk /usr/ports/INDEX-9 | cut -d '|' -f 6 | sort | uniq I'm preparing an update to fltk-1.3.0 and I would like to give you the chance to test your port against this new version. If no serious issues should raise in the next 15 days, I will commit the update (plus relative PORTREVISION bump on all dependent ports) on September 21st. It's going to be something in this direction: http://lists.freebsd.org/pipermail/cvs-ports/2010-March/191191.html Thank you for testing the patch available here: http://people.freebsd.org/~gahr/fltk-1.3.0.diff Kind Regards, The port graphics/qslim isn't building correctly with this new fltk. This patch seems to fix it. Even if it is garbled by the text processor/mail user, it should be obvious what it does - change the case of some letters in two occurrences of FL/Fl_File_Chooser.H Yes, that is correct. Can you commit this change at the same time as you commit the fltk update? It will be easier for you to get the timing correct than it will for me. Sure, I will keep that patch and commit it when I update fltk. Also, gmsh and vis5d+ (other ports that I maintain) seemed to build just fine. octave also built just fine, but that's maho's port, so I will let him have the final word. Thank you very much for looking at that! -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp ___ 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
About games/flightgear-aircrafts
Hi list, As you may know, games/flightgear-aircrafts is *HUGE*, way too big to be useable and buildable correctly, and, as a maintainer, a real pain to update. Today, if you just need one airplane from flightgear-aircrafts, you would have to download 350+ airplanes and more than 2 GB of data, which makes no sense at all. We have to get rid of that. I am thinking of two options : 1) providing only a subset of available airplanes (i.e. *not* every single airplane available on the FTP servers). This would be nice, but requires to set up a list of the best planes to include (top 30 best planes ?), and that list may not be the one every single user would have established. 2) removing the port and consider users have to install additional planes *manually*. After all, those airplanes are only addons ; limiting the ports to flightgear + flightgear-data, which already ship with several airplanes, does not seem crazy to me. A third option would have been to provide the full list of available airplanes but only select a few of them through OPTIONS, but I'd like to avoid going this way : this will not simplify the port at all, it will only make it harder to maintain as the OPTIONS list will be huge, and (maybe ?) pointless for the end-user. Flightgear users, I would go for option 2), but what do *you* think ? Best regards, -- Ganael LAPLANCHE ganael.laplan...@martymac.org http://www.martymac.org | http://contribs.martymac.org FreeBSD: martymac marty...@freebsd.org, http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: HEADS UP --- Update to x11-toolkits/fltk coming
On 2011-Sep-22, 16:30, Maho NAKATA wrote: Hi *, now I'm testing x11-toolkits/fltk for math/octave port. sorry for delay. I'm a bit behind schedule too, I'll probably get to it only next week! Happy testing ;) thanks From: Pietro Cerutti g...@freebsd.org Subject: Re: HEADS UP --- Update to x11-toolkits/fltk coming Date: Tue, 06 Sep 2011 15:53:31 +0200 On 2011-Sep-06, 08:28, Stephen Montgomery-Smith wrote: On 09/06/2011 07:32 AM, Pietro Cerutti wrote: On 2011-Sep-06, 07:28, Stephen Montgomery-Smith wrote: On 09/06/2011 06:26 AM, Stephen Montgomery-Smith wrote: On 09/06/2011 04:18 AM, Pietro Cerutti wrote: Hi, you're receiving this email because one of your ports depends on x11-toolkits/fltk, according to $ grep fltk /usr/ports/INDEX-9 | cut -d '|' -f 6 | sort | uniq I'm preparing an update to fltk-1.3.0 and I would like to give you the chance to test your port against this new version. If no serious issues should raise in the next 15 days, I will commit the update (plus relative PORTREVISION bump on all dependent ports) on September 21st. It's going to be something in this direction: http://lists.freebsd.org/pipermail/cvs-ports/2010-March/191191.html Thank you for testing the patch available here: http://people.freebsd.org/~gahr/fltk-1.3.0.diff Kind Regards, The port graphics/qslim isn't building correctly with this new fltk. This patch seems to fix it. Even if it is garbled by the text processor/mail user, it should be obvious what it does - change the case of some letters in two occurrences of FL/Fl_File_Chooser.H Yes, that is correct. Can you commit this change at the same time as you commit the fltk update? It will be easier for you to get the timing correct than it will for me. Sure, I will keep that patch and commit it when I update fltk. Also, gmsh and vis5d+ (other ports that I maintain) seemed to build just fine. octave also built just fine, but that's maho's port, so I will let him have the final word. Thank you very much for looking at that! -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgp8KszWJwYXq.pgp Description: PGP signature
Re: CFT: rt-4.0.2 port
On 14/09/2011 11:53, Matthew Seaman wrote: On 14/09/2011 11:37, Matthew Seaman wrote: This port has dependencies on three perl modules not already ported, so I've created new ports for those as well. You can download .shar archives of all four from: http://www.infracaninophile.co.uk/articles/rt40.html Ah. Apparently the three additional perl modules were added to the ports on 1st September. I'll update the rt40 shar shortly. My thanks to all those who have sent feedback so far. A couple of issues have been fixed, and I think it's now time to send-pr. One question: committers -- would you prefer this as a .shar for a new www/rt40 port, or as a diff against www/rt38 and repo-copy to www/rt40? Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: About games/flightgear-aircrafts
On 22 Sep 2011 09:11, Ganael LAPLANCHE ganael.laplan...@martymac.org wrote: Hi list, As you may know, games/flightgear-aircrafts is *HUGE*, way too big to be useable and buildable correctly, and, as a maintainer, a real pain to update. Today, if you just need one airplane from flightgear-aircrafts, you would have to download 350+ airplanes and more than 2 GB of data, which makes no sense at all. We have to get rid of that. I am thinking of two options : 1) providing only a subset of available airplanes (i.e. *not* every single airplane available on the FTP servers). This would be nice, but requires to set up a list of the best planes to include (top 30 best planes ?), and that list may not be the one every single user would have established. 2) removing the port and consider users have to install additional planes *manually*. After all, those airplanes are only addons ; limiting the ports to flightgear + flightgear-data, which already ship with several airplanes, does not seem crazy to me. A third option would have been to provide the full list of available airplanes but only select a few of them through OPTIONS, but I'd like to avoid going this way : this will not simplify the port at all, it will only make it harder to maintain as the OPTIONS list will be huge, and (maybe ?) pointless for the end-user. Flightgear users, I would go for option 2), but what do *you* think ? 4) add-on ports? Chris ___ 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: About games/flightgear-aircrafts
On Thu, Sep 22, 2011 at 10:03:38AM +0100, Chris Rees wrote: On 22 Sep 2011 09:11, Ganael LAPLANCHE ganael.laplan...@martymac.org wrote: Hi list, As you may know, games/flightgear-aircrafts is *HUGE*, way too big to be useable and buildable correctly, and, as a maintainer, a real pain to update. Today, if you just need one airplane from flightgear-aircrafts, you would have to download 350+ airplanes and more than 2 GB of data, which makes no sense at all. We have to get rid of that. I am thinking of two options : 1) providing only a subset of available airplanes (i.e. *not* every single airplane available on the FTP servers). This would be nice, but requires to set up a list of the best planes to include (top 30 best planes ?), and that list may not be the one every single user would have established. 2) removing the port and consider users have to install additional planes *manually*. After all, those airplanes are only addons ; limiting the ports to flightgear + flightgear-data, which already ship with several airplanes, does not seem crazy to me. A third option would have been to provide the full list of available airplanes but only select a few of them through OPTIONS, but I'd like to avoid going this way : this will not simplify the port at all, it will only make it harder to maintain as the OPTIONS list will be huge, and (maybe ?) pointless for the end-user. Flightgear users, I would go for option 2), but what do *you* think ? 4) add-on ports? yes, this seems to be the case with latex, works fine. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: CFT: rt-4.0.2 port
On 22.09.2011 10:32, Matthew Seaman wrote: On 14/09/2011 11:53, Matthew Seaman wrote: On 14/09/2011 11:37, Matthew Seaman wrote: This port has dependencies on three perl modules not already ported, so I've created new ports for those as well. You can download .shar archives of all four from: http://www.infracaninophile.co.uk/articles/rt40.html Ah. Apparently the three additional perl modules were added to the ports on 1st September. I'll update the rt40 shar shortly. My thanks to all those who have sent feedback so far. A couple of issues have been fixed, and I think it's now time to send-pr. One question: committers -- would you prefer this as a .shar for a new www/rt40 port, or as a diff against www/rt38 and repo-copy to www/rt40? Please send it as a diff against rt38, as we'll do a repo copy. Thanks, Florian ___ 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: Ruby
Hi Chris, I see; these things always might happen. Can you tell me where I can find a summary of issues that come with this version? I then can check whether this might affect my system or not. For the time being I will stick to 1.9. Thanks, Jos Chrispijn Chris Rees: Unfortunately, although huge efforts were made by the ruby team it turned out that there were some edge cases that made the switch really difficult to some people, so it was decided to revert the change in defaults. If 1.9 works for you, great, but for now you'll need RUBY_DEFAULT_VER=1.9 in /etc/make.conf. Please keep testing 1.9! Chris ___ 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: About games/flightgear-aircrafts
On Thu, 22 Sep 2011 10:07:40 +0100, Anton Shterenlikht wrote Chris, Anton, Thanks for your feedback. 4) add-on ports? yes, this seems to be the case with latex, works fine. I am not sure to understand what you mean exactly. Could you be more precise ? -- Ganael LAPLANCHE ganael.laplan...@martymac.org http://www.martymac.org | http://contribs.martymac.org FreeBSD: martymac marty...@freebsd.org, http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: CFT: rt-4.0.2 port
On 22/09/2011 10:20, Florian Smeets wrote: One question: committers -- would you prefer this as a .shar for a new www/rt40 port, or as a diff against www/rt38 and repo-copy to www/rt40? Please send it as a diff against rt38, as we'll do a repo copy. Done. http://www.freebsd.org/cgi/query-pr.cgi?pr=160901 Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Ports problem with py-vte.
Hiya Im actually trying to install the port terminator, but the dependacy port it tripping over itself. Would anyone know how I can go about fixing this? Kind Regards Brent Clark [root@bclark-laptop /usr/ports/x11-toolkits/py-vte]# make install clean === Building for py27-vte-0.26.2 CC vtemodule_la-vtemodule.lo vtemodule.c:23:23: error: pygobject.h: No such file or directory vtemodule.c:24:25: error: pygtk/pygtk.h: No such file or directory In file included from vtemodule.c:25: ../src/vte.h:22:18: error: glib.h: No such file or directory ../src/vte.h:23:21: error: gio/gio.h: No such file or directory ../src/vte.h:24:25: error: pango/pango.h: No such file or directory ../src/vte.h:25:21: error: gtk/gtk.h: No such file or directory In file included from ../src/vte.h:29, from vtemodule.c:25: ../src/vtepty.h:26:25: error: glib-object.h: No such file or directory In file included from ../src/vte.h:29, from vtemodule.c:25: ../src/vtepty.h:42: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'typedef' ../src/vtepty.h:64: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'vte_pty_error_quark' ../src/vtepty.h:88: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'vte_pty_get_type' ../src/vtepty.h:91: error: expected declaration specifiers or '...' before 'GError' ../src/vtepty.h:94: error: expected declaration specifiers or '...' before 'GError' ../src/vtepty.h:102: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'vte_pty_get_size' ../src/vtepty.h:107: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'vte_pty_set_size' ../src/vtepty.h:112: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'vte_pty_set_utf8' In file included from ../src/vte.h:30, from vtemodule.c:25: ../src/vtetypebuiltins.h:13: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'G_BEGIN_DECLS' ../src/vtetypebuiltins.h:18: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'vte_terminal_cursor_blink_mode_get_type' ../src/vtetypebuiltins.h:20: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'vte_terminal_cursor_shape_get_type' ../src/vtetypebuiltins.h:22: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'vte_terminal_write_flags_get_type' ../src/vtetypebuiltins.h:26: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'vte_pty_flags_get_type' ../src/vtetypebuiltins.h:28: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'vte_pty_error_get_type' ../src/vtetypebuiltins.h:32: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'vte_terminal_anti_alias_get_type' In file included from vtemodule.c:25: ../src/vte.h:35: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'G_BEGIN_DECLS' ../src/vte.h:66: error: expected specifier-qualifier-list before 'GtkWidget' ../src/vte.h:91: error: expected specifier-qualifier-list before 'GtkWidgetClass' ../src/vte.h:230: error: expected specifier-qualifier-list before 'GdkColor' ../src/vte.h:239: error: expected specifier-qualifier-list before 'GdkColor' ../src/vte.h:243: error: expected declaration specifiers or '...' before '*' token ../src/vte.h:243: error: expected ')' before '*' token ../src/vte.h:249: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'vte_terminal_get_type' ../src/vte.h:251: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token ../src/vte.h:253: error: expected ')' before '*' token ../src/vte.h:257: error: expected ')' before '*' token ../src/vte.h:260: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'vte_terminal_fork_command_full' ../src/vte.h:273: error: expected ')' before '*' token ../src/vte.h:274: error: expected ')' before '*' token ../src/vte.h:275: error: expected ')' before '*' token ../src/vte.h:279: error: expected ')' before '*' token ../src/vte.h:280: error: expected ')' before '*' token ../src/vte.h:281: error: expected ')' before '*' token ../src/vte.h:282: error: expected ')' before '*' token ../src/vte.h:285: error: expected ')' before '*' token ../src/vte.h:286: error: expected ')' before '*' token ../src/vte.h:289: error: expected ')' before '*' token ../src/vte.h:293: error: expected ')' before '*' token ../src/vte.h:294: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'vte_terminal_get_audible_bell' ../src/vte.h:295: error: expected ')' before '*' token ../src/vte.h:296: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'vte_terminal_get_visible_bell' ../src/vte.h:297: error: expected ')' before '*' token ../src/vte.h:298: error: expected ')' before '*' token ../src/vte.h:299: error: expected ')' before '*' token ../src/vte.h:303: error: expected ')' before '*' token ../src/vte.h:305: error: expected ')' before '*' token ../src/vte.h:307: error: expected ')' before '*' token ../src/vte.h:309: error: expected ')' before '*' token
Re: Status of cups-base and avahi-app?
From Chris Rees cr...@freebsd.org: Well... you lose avahi, which is a zeroconf implementation, but you're probably just better off with samba. The BROKEN message references http://www.avahi.org/ticket/303 -- look there for more information on why it's marked as such. Chris I found that avahi bug ticket, noticed some Linuxes, including Ubuntu, manage to work around the bug. I guess I'll turn off the avahi option. What counts is getting the printer to work with hplip. I might also try to build wine and see if the MS-Windows driver for the printer works that way. Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: About games/flightgear-aircrafts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 9/22/11 5:28 AM, Ganael LAPLANCHE wrote: On Thu, 22 Sep 2011 10:07:40 +0100, Anton Shterenlikht wrote Chris, Anton, Thanks for your feedback. 4) add-on ports? yes, this seems to be the case with latex, works fine. I am not sure to understand what you mean exactly. Could you be more precise ? I'm not familiar with the flightgear and latex ports, but it appears that latex is structured with a base port and a number of ports for add-ons. Have a look at the output of ls -ld /usr/ports/print/latex-*, and you'll see the add-on ports. If you can break the flightgear airplanes (or subsets of airplanes) into a number of add-on ports, that would be one way to avoid the huge download problem, as well as an excessive number of OPTIONS in the base port. Of course, the add-on port idea assumes that airplanes can be downloaded individually in some fashion. Hope that helps, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk57L6gACgkQ0sRouByUApD7eQCfQ2y2n8/ZzabCc3sSdzV/xGQE 90EAnjD8bvcVs4Zea6hNK2AooO3ezvGf =sh/Y -END PGP SIGNATURE- ___ 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: About games/flightgear-aircrafts
On Thu, 22 Sep 2011 08:52:56 -0400, Greg Larkin wrote Hi Greg, [...] If you can break the flightgear airplanes (or subsets of airplanes) into a number of add-on ports, that would be one way to avoid the huge download problem, as well as an excessive number of OPTIONS in the base port. Of course, the add-on port idea assumes that airplanes can be downloaded individually in some fashion. Thanks for this explanation. I had thought about that option too, but the same questions as my first solution remain : what should be the list of the available ports ? I really have no idea here : any craft may be interesting to players. Also, if this list could be established, why not keep a single port (which would then be *a lot* easier to maintain) ? To sum um, in my opinion, there are in really 2 options : 1) Limit the port to a few selected aircrafts = (either in one port or split) 2) Remove the port I can go for 1), but I would need help to establish the list of aircrafts you'd like... :p Best regards, -- Ganael LAPLANCHE ganael.laplan...@martymac.org http://www.martymac.org | http://contribs.martymac.org FreeBSD: martymac marty...@freebsd.org, http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: About games/flightgear-aircrafts
On Thu, Sep 22, 2011 at 01:35:48PM +0200, Ganael LAPLANCHE wrote: On Thu, 22 Sep 2011 10:43:47 +0100, Anton Shterenlikht wrote Hi Anton, print/teTeX is quite old. However, it's a critical port for many people, and there is no easy update or replacement (tex-live work is ongoing, I think). So, rather than updating the whole of teTeX, hrs@ has been adding new (or newer) latex packages as separate add-on ports, e.g. print/latex-nomencl or print/latex-chapterfolder. This way, user who need newer latex features, can easily get them, still within the ports framework. Others, who only need the core of latex, do not need to install those add-on ports, e.g. textproc/docproj-jadetex. Thanks for this clarification. In my opinion, games/flightgear-aircrafts can already been considered as an addon port : none of the aircrafts installed by this port is mandatory to have the game run correctly. The main problem I face is that several distfiles change regularly, and keeping a list of 350+ aircrafts distfiles up-to-date within a single port is a real pain. The other problem is being able to provide the distfiles for a longer time than the official mirrors do : it would require to set up an additional mirror to collect them all and it would require a lot of space to do so. So, if I understand correctly, your 4th suggestion would be to split this huge port up into single aircraft ones ? If yes, the same question remains : what should be the list of selected ports ? And if this list should be limited to, say, 30 ports, why not provide them in a single port (which would then be a lot easier to maintain) ? sorry, no idea. My point was just that sometimes it's easier to split a large port into a smaller core, and several add-on ports. Best regards, PS : ports@ not included in your previous answer, is it voluntary ? just forgot -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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: About games/flightgear-aircrafts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 9/22/11 9:13 AM, Ganael LAPLANCHE wrote: On Thu, 22 Sep 2011 08:52:56 -0400, Greg Larkin wrote Hi Greg, [...] If you can break the flightgear airplanes (or subsets of airplanes) into a number of add-on ports, that would be one way to avoid the huge download problem, as well as an excessive number of OPTIONS in the base port. Of course, the add-on port idea assumes that airplanes can be downloaded individually in some fashion. Thanks for this explanation. I had thought about that option too, but the same questions as my first solution remain : what should be the list of the available ports ? I really have no idea here : any craft may be interesting to players. Also, if this list could be established, why not keep a single port (which would then be *a lot* easier to maintain) ? To sum um, in my opinion, there are in really 2 options : 1) Limit the port to a few selected aircrafts = (either in one port or split) 2) Remove the port I can go for 1), but I would need help to establish the list of aircrafts you'd like... :p Best regards, I don't use flightgear, so others would have a better opinion than me about how to partition the airplane ports. Is there a forum on the upstream distro site where you could ask? You can also break them by first letter of the distfile names, combining where appropriate. An analysis of the number of distfiles per first letter of the filename yields: 2 1 7 16 a 35 b 30 c 30 d 29 e 5 f 28 g 5 h 18 i 2 j 9 k 8 l 17 m 22 n 6 o 4 p 22 q 1 r 10 s 32 t 8 u 2 v 7 w 1 x 2 y 3 z 2 You could combine some letters together and make a bunch of add-on ports with ~30 planes per port. Regards, Greg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk57OlkACgkQ0sRouByUApCD7wCguk8h/fk1QKuBP1kW6B+b4ebo C2sAn2krZJC5wtQpq1AZk5MDpoEIZ9dj =fgl+ -END PGP SIGNATURE- ___ 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: About games/flightgear-aircrafts
On 9/22/2011 9:38 AM, Greg Larkin wrote: I don't use flightgear, so others would have a better opinion than me about how to partition the airplane ports. Is there a forum on the upstream distro site where you could ask? You can also break them by first letter of the distfile names, combining where appropriate. An analysis of the number of distfiles per first letter of the filename yields: 2 1 7 16 a 35 b 30 c 30 d 29 e 5 f 28 g 5 h 18 i 2 j 9 k 8 l 17 m 22 n 6 o 4 p 22 q 1 r 10 s 32 t 8 u 2 v 7 w 1 x 2 y 3 z 2 You could combine some letters together and make a bunch of add-on ports with ~30 planes per port. I don't use this program either, but my first reaction was to break it into broad categories. For example: aircraft-required aircraft-25-most-popular aircraft-civilian-prop aircraft-civilian-jet aircraft-military-prop aircraft-military-jet Other categories may suggest themselves to those more familiar with the game. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: HEADS UP --- Update to x11-toolkits/fltk coming
Hi gahr, your fltk update seems to be ok to me (math/octave). thanks Nakata Maho From: Pietro Cerutti g...@freebsd.org Subject: Re: HEADS UP --- Update to x11-toolkits/fltk coming Date: Thu, 22 Sep 2011 10:32:02 +0200 On 2011-Sep-22, 16:30, Maho NAKATA wrote: Hi *, now I'm testing x11-toolkits/fltk for math/octave port. sorry for delay. I'm a bit behind schedule too, I'll probably get to it only next week! Happy testing ;) thanks From: Pietro Cerutti g...@freebsd.org Subject: Re: HEADS UP --- Update to x11-toolkits/fltk coming Date: Tue, 06 Sep 2011 15:53:31 +0200 On 2011-Sep-06, 08:28, Stephen Montgomery-Smith wrote: On 09/06/2011 07:32 AM, Pietro Cerutti wrote: On 2011-Sep-06, 07:28, Stephen Montgomery-Smith wrote: On 09/06/2011 06:26 AM, Stephen Montgomery-Smith wrote: On 09/06/2011 04:18 AM, Pietro Cerutti wrote: Hi, you're receiving this email because one of your ports depends on x11-toolkits/fltk, according to $ grep fltk /usr/ports/INDEX-9 | cut -d '|' -f 6 | sort | uniq I'm preparing an update to fltk-1.3.0 and I would like to give you the chance to test your port against this new version. If no serious issues should raise in the next 15 days, I will commit the update (plus relative PORTREVISION bump on all dependent ports) on September 21st. It's going to be something in this direction: http://lists.freebsd.org/pipermail/cvs-ports/2010-March/191191.html Thank you for testing the patch available here: http://people.freebsd.org/~gahr/fltk-1.3.0.diff Kind Regards, The port graphics/qslim isn't building correctly with this new fltk. This patch seems to fix it. Even if it is garbled by the text processor/mail user, it should be obvious what it does - change the case of some letters in two occurrences of FL/Fl_File_Chooser.H Yes, that is correct. Can you commit this change at the same time as you commit the fltk update? It will be easier for you to get the timing correct than it will for me. Sure, I will keep that patch and commit it when I update fltk. Also, gmsh and vis5d+ (other ports that I maintain) seemed to build just fine. octave also built just fine, but that's maho's port, so I will let him have the final word. Thank you very much for looking at that! -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: HEADS UP --- Update to x11-toolkits/fltk coming
2011/9/22 Maho NAKATA cha...@mac.com: Hi gahr, your fltk update seems to be ok to me (math/octave). That's a good news. wen thanks Nakata Maho From: Pietro Cerutti g...@freebsd.org Subject: Re: HEADS UP --- Update to x11-toolkits/fltk coming Date: Thu, 22 Sep 2011 10:32:02 +0200 On 2011-Sep-22, 16:30, Maho NAKATA wrote: Hi *, now I'm testing x11-toolkits/fltk for math/octave port. sorry for delay. I'm a bit behind schedule too, I'll probably get to it only next week! Happy testing ;) thanks From: Pietro Cerutti g...@freebsd.org Subject: Re: HEADS UP --- Update to x11-toolkits/fltk coming Date: Tue, 06 Sep 2011 15:53:31 +0200 On 2011-Sep-06, 08:28, Stephen Montgomery-Smith wrote: On 09/06/2011 07:32 AM, Pietro Cerutti wrote: On 2011-Sep-06, 07:28, Stephen Montgomery-Smith wrote: On 09/06/2011 06:26 AM, Stephen Montgomery-Smith wrote: On 09/06/2011 04:18 AM, Pietro Cerutti wrote: Hi, you're receiving this email because one of your ports depends on x11-toolkits/fltk, according to $ grep fltk /usr/ports/INDEX-9 | cut -d '|' -f 6 | sort | uniq I'm preparing an update to fltk-1.3.0 and I would like to give you the chance to test your port against this new version. If no serious issues should raise in the next 15 days, I will commit the update (plus relative PORTREVISION bump on all dependent ports) on September 21st. It's going to be something in this direction: http://lists.freebsd.org/pipermail/cvs-ports/2010-March/191191.html Thank you for testing the patch available here: http://people.freebsd.org/~gahr/fltk-1.3.0.diff Kind Regards, The port graphics/qslim isn't building correctly with this new fltk. This patch seems to fix it. Even if it is garbled by the text processor/mail user, it should be obvious what it does - change the case of some letters in two occurrences of FL/Fl_File_Chooser.H Yes, that is correct. Can you commit this change at the same time as you commit the fltk update? It will be easier for you to get the timing correct than it will for me. Sure, I will keep that patch and commit it when I update fltk. Also, gmsh and vis5d+ (other ports that I maintain) seemed to build just fine. octave also built just fine, but that's maho's port, so I will let him have the final word. Thank you very much for looking at that! -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: About games/flightgear-aircrafts
On Thu, 22 Sep 2011, Ganael LAPLANCHE wrote: 1) providing only a subset of available airplanes (i.e. *not* every single airplane available on the FTP servers). This would be nice, but requires to set up a list of the best planes to include (top 30 best planes ?), and that list may not be the one every single user would have established. 2) removing the port and consider users have to install additional planes *manually*. After all, those airplanes are only addons ; limiting the ports to flightgear + flightgear-data, which already ship with several airplanes, does not seem crazy to me. A third option would have been to provide the full list of available airplanes but only select a few of them through OPTIONS, but I'd like to avoid going this way : this will not simplify the port at all, it will only make it harder to maintain as the OPTIONS list will be huge, and (maybe ?) pointless for the end-user. Flightgear users, I would go for option 2), but what do *you* think ? #2 is reasonable, IMO. Other options, like breaking it up into multiple ports, would not make it easier to maintain and might be more difficult for users. (Note: aircraft is both singular and plural, so the port name really should be just flightgear-aircraft.) ___ 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: About games/flightgear-aircrafts
On Thu, Sep 22, 2011 at 09:57:58AM -0400, Robert Huff wrote: I don't use this program either, but my first reaction was to break it into broad categories. For example: aircraft-required aircraft-25-most-popular aircraft-civilian-prop aircraft-civilian-jet aircraft-military-prop aircraft-military-jet Other categories may suggest themselves to those more familiar with the game. A civialian-aerobatic category could be sensible. Also, a distinction between turbo-prop and piston engine craft could make sense. Turbo props and piston engines are very different categories in aviation and should appeal to rather different players and simulator use cases. -- Guido Falsi m...@madpilot.net ___ 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: Circular dependency in devel/doxygen?
On Tue, Sep 20, 2011 at 3:47 AM, tho...@freebsd.org wrote: Hey everyone, I maintain devel/doxygen (sorry I didn't add my 2 cents earlier, I've been a bit busy) and was looking at this particular thread. I know someone filed a PR regarding the circular dependency, stating that it might be best to split apart doxygen so one port builds just the program and another port build just the documentation. I am not sure if that is the best thing to do or not. I've been wanting to push out an update to doxygen but this has been a stopping block for me. Naram Qashat It seems strange to me that doxygen would have audio dependencies, or is doxygen supposed to work with a speech synthesizer? What dependencies would doxygen documentation have? Anything circular? The problem is that doxygen has a build dependancy on graphics graphviz when building it's documentation, and when you select certain options, you can cause a circular dependancy. See below for one example: audio/pulseaudio - audio/jack -- devel/doxygen --- graphics/graphviz graphics/devil - devel/sdl12 -- audio/pulseaudio Scot ___ 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: About games/flightgear-aircrafts
On Thu, 22 Sep 2011 09:38:33 -0400, Greg Larkin wrote You can also break them by first letter of the distfile names, combining where appropriate. [...] On Thu, 22 Sep 2011 09:57:58 -0400, Robert Huff wrote my first reaction was to break it into broad categories. For example: aircraft-required aircraft-25-most-popular aircraft-civilian-prop [...] On Thu, 22 Sep 2011 16:58:03 +0200, Guido Falsi wrote A civialian-aerobatic category could be sensible. [...] Greg, Robert, Guido, thanks for your suggestions ; anyway, this would not solve one of the problems : maintainability of the port :/ On Thu, 22 Sep 2011 08:11:39 -0600 (MDT), Warren Block wrote #2 is reasonable, IMO. Other options, like breaking it up into multiple ports, would not make it easier to maintain and might be more difficult for users. Warren, I agree with you : it would make the port even more complex. From a maintainer port of view, we will still have to keep up-to-date with those 350+ zip files which regularly change upstream, but will now have to deal with sorting them and updating several different ports. From a user point of view, it would also be a pain : users would have to browse into each category ports to be able to get all the planes they need. I am not sure this is the right way to go :/ I would also vote for #2, or, if we can get a limited list of good airplanes, option #1. I will try to find if I can get a list of top planes on FLightGear website, but I have not seen such a page so far. (Note: aircraft is both singular and plural, so the port name really should be just flightgear-aircraft.) Thanks, I'll fix its name if we can manage to keep this port alive :) Best regards, -- Ganael LAPLANCHE ganael.laplan...@martymac.org http://www.martymac.org | http://contribs.martymac.org FreeBSD: martymac marty...@freebsd.org, http://www.FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Circular dependency in devel/doxygen?
On Thu, Sep 22, 2011 at 10:09:57AM -0500, Scot Hetzel wrote:
Date: Thu, 22 Sep 2011 10:09:57 -0500
From: Scot Hetzel swhet...@gmail.com
Subject: Re: Circular dependency in devel/doxygen?
To: tho...@freebsd.org, muel...@freebsd.org
Cc: freebsd-ports@freebsd.org
On Tue, Sep 20, 2011 at 3:47 AM, tho...@freebsd.org wrote:
Hey everyone, I maintain devel/doxygen (sorry I didn't add my 2 cents
earlier, I've been a bit busy) and was looking at this particular thread.
I
know someone filed a PR regarding the circular dependency, stating that it
might be best to split apart doxygen so one port builds just the program
and
another port build just the documentation. I am not sure if that is the
best thing to do or not. I've been wanting to push out an update to doxygen
but this has been a stopping block for me.
Naram Qashat
It seems strange to me that doxygen would have audio dependencies, or is
doxygen supposed to work with a speech synthesizer?
What dependencies would doxygen documentation have? Anything circular?
The problem is that doxygen has a build dependancy on graphics
graphviz when building it's documentation, and when you select certain
options, you can cause a circular dependancy. See below for one
example:
audio/pulseaudio
- audio/jack
-- devel/doxygen
--- graphics/graphviz
graphics/devil
- devel/sdl12
-- audio/pulseaudio
Scot
___
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
time for my dime's worth of questions. is there any way of
building that audio/video app or plugin that works with linux?
it is from adobe and works with pc-bsd. we've got a free
version. is it flash? this is the main reason i switched
to ubuntu for my desktop. so i can watch sites like pbs.org
and npr.org. stream igages with sound. in my opinion, it
is this that stalls the broader use of all of the berkeley
distributions.
--
Gary Kline kl...@thought.org http://www.thought.org Public Service Unix
Journey Toward the Dawn, E-Book: http://www.thought.org
The 8.51a release of Jottings: http://jottings.thought.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: CFT: security/openssh-portable 5.8p2
Mainly features introduced by external patches should be tested. They work for me, but maybe someone will find some regressions. ___ 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
