Date: Sat, 09 May 2009 09:19:59 +0900 (JST) From: Maho NAKATA <chat95@mac.com> To: stephen@missouri.edu Cc: freebsd-ports@freebsd.org Subject: Re: octave forge update issues Message-ID: <20090509.091959.193729934.chat95@mac.com> In-Reply-To: <4A04B4D2.8040204@missouri.edu> References: <4A04B4D2.8040204@missouri.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
----Security_Multipart(Sat_May__9_09_19_59_2009_186)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Stephen Montgomery-Smith <stephen@missouri.edu> Subject: octave forge update issues Date: Fri, 08 May 2009 17:40:18 -0500 > I am the octave-forge maintainer. > > The octave forge source files have been updated. Quite a few of the > new source packages require octave-devel (3.1.55) instead of octave > itself. I am not quite sure what to do. I was hoping some end users > could give me their opinion. Here are some options: > > 1. Leave it all alone until octave catches up to octave-devel. +1 I'd like to leave octave-devel port as leaf ports as if some conflict can happen. > 2. Make octave-forge pull in octave-devel as a dependency instead of > octave. Some may want to test some of new octave-forge packages so is it possible to add some knob so that user can select which one to depend? Best, -- Nakata Maho http://accc.riken.jp/maho/ , http://ja.openoffice.org/ Nakata Maho's PGP public keys: http://accc.riken.jp/maho/maho.pgp.txt ----Security_Multipart(Sat_May__9_09_19_59_2009_186)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEABECAAYFAkoEzDEACgkQpcQqaPiEzfl7zgCgxPx/vKBFGe9hlIpKhw0+Zo+B wpUAmgLYfVKwlDNlBrg0tUiLP/vIG0AN =5ZXH -----END PGP SIGNATURE----- ----Security_Multipart(Sat_May__9_09_19_59_2009_186)----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090509.091959.193729934.chat95>