Re: Nuke some Ocaml ports
On 02/28, Edd Barrett wrote: > On Mon, Feb 27, 2017 at 10:31:21PM +0100, Christopher Zimmermann wrote: > > On 2017-02-27 Daniel Dickman wrote: > > > > > > > > devel/utop > > > > > > please no. > > > > I acknowlegde this is a very useful tool for the OCaml developer, but > > it also has heavy dependencies. > > Since most OCaml users on OpenBSD use opam, maintaining this stuff is a > > burden. > > I also would like to keep utop if possible. Can you install utop from > opam? If so you can probably nuke the port. FWIW, I have never used > opam, but then, I only dabbled in OCaml. utop is indeed installable from opam. I always use it thusly. I classify it as a programmer's tool, not an end-usr tool and thus I would indeed like to remove the port (and the resulting dangling dependencies as pointed out by Chris). Ken > > > As an alternative, when utop is unavailable, I use `rlwrap ocaml` to get > > nice command line editing. > > I recall that I didn't get on with this solution for some reason. > > -- > Best Regards > Edd Barrett > > http://www.theunixzoo.co.uk >
Re: Nuke some Ocaml ports
On 27 Feb 2017, at 20:58, Daniel Dickman wrote: > > > >> On Feb 27, 2017, at 3:23 PM, Christopher Zimmermann >> wrote: >> >>> On 2017-02-27 Kenneth R Westerback wrote: >>> >>> Anyway, I'm happy to do the dirty work of nuking any or all of these >>> ports and then continuing the process of weeding out ports that >>> might be more useful to get people sourcing from opam. >>> >>> And thus hopefully making it simpler to keep us on the ocaml bleeding >>> edge. >>> >>> Thoughts? >>> >>> Ken >>> >>> The numbers // >>> >>> Anil: >>> ./databases/ocaml-postgresql 3.2.1/4.0.1/4.0.1 (master & homepage dead?) >>> ./databases/ocaml-sqlite3 2.0.9/4.1.2/4.1.2 (master & homepage dead?) >>> ./devel/ocaml-calendar 2.03.2/2.0.4/2.03.2 >>> ./graphics/ocaml-camlimages 4.2.1/4.2.1/4.2.3 >>> ./security/ocaml-cryptokit 1.10/1.11/1.11 >>> ./textproc/ocaml-rss 2.0/2.2.1/2.2.2 >>> ./textproc/ocaml-xml-light 2.2/2.4/2.4 >>> ./textproc/ocaml-xmlm 1.2.0/1.2.0/1.2.0 >>> >>> Chrisz >>> ./devel/ocaml-batteries 2.5.0/2.5.3/2.5.3 >>> ./devel/ocaml-net 4.0.2/4.1.2/4.1.2 >> >> OK chrisz@ >> >>> Edd: >>> ./devel/ocaml-mlgmp 0.13/20120224/20120224 >>> >>> None: >>> ./devel/ocaml-bitstring 2.0.4/2.0.4/2.1.0 (google code!?) >>> ./devel/ocaml-curses 1.0.3/1.0.3/1.0.3 >>> ./textproc/ocaml-csv 1.4.1/1.6/1.6 >> >> OK chrisz@ >> >> >> I would like to add more to this list: >> >> devel/utop > > please no. > >> devel/ocaml-lambda-term >> devel/ocaml-zed >> devel/ocaml-lwt >> devel/ocaml-menhir > > please no. it's required for compcert. I'm ok with deleting the intermediate ports, but we should indeed keep anything that is required for Compcert in the ports tree. It's very useful to have a binary package of it. As for utop, I'd be happy just installing that through OPAM. You typically also need to install libraries with utop to make it useful, and that's difficult to do with a system OCaml and a port-installed OPAM (it can use the system compiler fine, but libraries must be managed all through opam or not at all). Anil
Re: Nuke some Ocaml ports
On Mon, Feb 27, 2017 at 10:31:21PM +0100, Christopher Zimmermann wrote: > On 2017-02-27 Daniel Dickman wrote: > > > > > > devel/utop > > > > please no. > > I acknowlegde this is a very useful tool for the OCaml developer, but > it also has heavy dependencies. > Since most OCaml users on OpenBSD use opam, maintaining this stuff is a > burden. I also would like to keep utop if possible. Can you install utop from opam? If so you can probably nuke the port. FWIW, I have never used opam, but then, I only dabbled in OCaml. > As an alternative, when utop is unavailable, I use `rlwrap ocaml` to get > nice command line editing. I recall that I didn't get on with this solution for some reason. -- Best Regards Edd Barrett http://www.theunixzoo.co.uk
Re: Nuke some Ocaml ports
On 2017-02-27 Daniel Dickman wrote: > > On Feb 27, 2017, at 3:23 PM, Christopher Zimmermann > > wrote: > > I would like to add more to this list: > > > > devel/utop > > please no. I acknowlegde this is a very useful tool for the OCaml developer, but it also has heavy dependencies. Since most OCaml users on OpenBSD use opam, maintaining this stuff is a burden. Is using opam no option for you? As an alternative, when utop is unavailable, I use `rlwrap ocaml` to get nice command line editing. > > devel/ocaml-lambda-term > > devel/ocaml-zed > > devel/ocaml-lwt > > devel/ocaml-menhir > > please no. it's required for compcert. You talk about menhir only here? That's no problem. It has no dependencies. But still is opam no option for you? If not, why? Christopher -- http://gmerlin.de OpenPGP: http://gmerlin.de/christopher.pub 2779 7F73 44FD 0736 B67A C410 69EC 7922 34B4 2566 pgpubQdXsaYoD.pgp Description: OpenPGP digital signature
Re: Nuke some Ocaml ports
> On Feb 27, 2017, at 3:23 PM, Christopher Zimmermann > wrote: > >> On 2017-02-27 Kenneth R Westerback wrote: >> >> Anyway, I'm happy to do the dirty work of nuking any or all of these >> ports and then continuing the process of weeding out ports that >> might be more useful to get people sourcing from opam. >> >> And thus hopefully making it simpler to keep us on the ocaml bleeding >> edge. >> >> Thoughts? >> >> Ken >> >> The numbers // >> >> Anil: >> ./databases/ocaml-postgresql 3.2.1/4.0.1/4.0.1 (master & homepage dead?) >> ./databases/ocaml-sqlite3 2.0.9/4.1.2/4.1.2 (master & homepage dead?) >> ./devel/ocaml-calendar 2.03.2/2.0.4/2.03.2 >> ./graphics/ocaml-camlimages 4.2.1/4.2.1/4.2.3 >> ./security/ocaml-cryptokit 1.10/1.11/1.11 >> ./textproc/ocaml-rss 2.0/2.2.1/2.2.2 >> ./textproc/ocaml-xml-light 2.2/2.4/2.4 >> ./textproc/ocaml-xmlm 1.2.0/1.2.0/1.2.0 >> >> Chrisz >> ./devel/ocaml-batteries 2.5.0/2.5.3/2.5.3 >> ./devel/ocaml-net 4.0.2/4.1.2/4.1.2 > > OK chrisz@ > >> Edd: >> ./devel/ocaml-mlgmp 0.13/20120224/20120224 >> >> None: >> ./devel/ocaml-bitstring 2.0.4/2.0.4/2.1.0 (google code!?) >> ./devel/ocaml-curses 1.0.3/1.0.3/1.0.3 >> ./textproc/ocaml-csv 1.4.1/1.6/1.6 > > OK chrisz@ > > > I would like to add more to this list: > > devel/utop please no. > devel/ocaml-lambda-term > devel/ocaml-zed > devel/ocaml-lwt > devel/ocaml-menhir please no. it's required for compcert. > devel/ocaml-ppx-tools > devel/ocaml-react > devel/ocaml-uutf > devel/omake > security/ocaml-ssl > textproc/ocaml-csv > textproc/ocaml-text > > > anyone using lang/obc ?? > > > I'd try an opam install before removing the port, just to be sure you > don't throw patches out we might want to keep. > > > Christopher > > > -- > http://gmerlin.de > OpenPGP: http://gmerlin.de/christopher.pub > 2779 7F73 44FD 0736 B67A C410 69EC 7922 34B4 2566
Re: Nuke some Ocaml ports
> On Feb 27, 2017, at 11:57 AM, Kenneth R Westerback > wrote: > > > None: > ./devel/ocaml-bitstring 2.0.4/2.0.4/2.1.0 (google code!?) > originally was needed for lang/compcert on powerpc, but believe newer versions of compcert no longer require it. so ok with me on this one.
Re: Nuke some Ocaml ports
On 2017-02-27 Kenneth R Westerback wrote: > > Anyway, I'm happy to do the dirty work of nuking any or all of these > ports and then continuing the process of weeding out ports that > might be more useful to get people sourcing from opam. > > And thus hopefully making it simpler to keep us on the ocaml bleeding > edge. > > Thoughts? > > Ken > > The numbers // > > Anil: > ./databases/ocaml-postgresql 3.2.1/4.0.1/4.0.1 (master & homepage dead?) > ./databases/ocaml-sqlite3 2.0.9/4.1.2/4.1.2 (master & homepage dead?) > ./devel/ocaml-calendar 2.03.2/2.0.4/2.03.2 > ./graphics/ocaml-camlimages 4.2.1/4.2.1/4.2.3 > ./security/ocaml-cryptokit 1.10/1.11/1.11 > ./textproc/ocaml-rss 2.0/2.2.1/2.2.2 > ./textproc/ocaml-xml-light 2.2/2.4/2.4 > ./textproc/ocaml-xmlm 1.2.0/1.2.0/1.2.0 > > Chrisz > ./devel/ocaml-batteries 2.5.0/2.5.3/2.5.3 > ./devel/ocaml-net 4.0.2/4.1.2/4.1.2 OK chrisz@ > Edd: > ./devel/ocaml-mlgmp 0.13/20120224/20120224 > > None: > ./devel/ocaml-bitstring 2.0.4/2.0.4/2.1.0 (google code!?) > ./devel/ocaml-curses 1.0.3/1.0.3/1.0.3 > ./textproc/ocaml-csv 1.4.1/1.6/1.6 OK chrisz@ I would like to add more to this list: devel/utop devel/ocaml-lambda-term devel/ocaml-zed devel/ocaml-lwt devel/ocaml-menhir devel/ocaml-ppx-tools devel/ocaml-react devel/ocaml-uutf devel/omake security/ocaml-ssl textproc/ocaml-csv textproc/ocaml-text anyone using lang/obc ?? I'd try an opam install before removing the port, just to be sure you don't throw patches out we might want to keep. Christopher -- http://gmerlin.de OpenPGP: http://gmerlin.de/christopher.pub 2779 7F73 44FD 0736 B67A C410 69EC 7922 34B4 2566 pgp8KvyesbAmL.pgp Description: OpenPGP digital signature
Re: Nuke some Ocaml ports
Hi Ken, On Mon, Feb 27, 2017 at 11:57:10AM -0500, Kenneth R Westerback wrote: > Edd: > ./devel/ocaml-mlgmp 0.13/20120224/20120224 I think I was experimenting with this during my PhD. I certainly don't use it now. Nothing depends on it. It can probably go. -- Best Regards Edd Barrett http://www.theunixzoo.co.uk
