NEW: misc/libcpucycles

2023-08-03 Thread Miguel Landaeta
r most architectures. libcpucycles also understands common OS-level mechanisms, which give varying levels of accuracy. Maintainer: Miguel Landaeta WWW: https://cpucycles.cr.yp.to/ -- Miguel Landaeta, miguel at miguel.cc secure email with PGP 0x6E608B637D8967E9 available at http://keyserver.pgp.c

Re: NEW: misc/libcpucycles

2023-08-04 Thread Miguel Landaeta
ex: doc/man/cpucycles.3 > > Unless necessary to make it work, I'd skip those. Ack. It makes more sense to fix it upstream. -- Miguel Landaeta, miguel at miguel.cc secure email with PGP 0x6E608B637D8967E9 available at http://keyserver.pgp.com/ "Faith means not wanting

Re: NEW: misc/libcpucycles

2023-08-07 Thread Miguel Landaeta
Ping? On Fri, Aug 4, 2023 at 10:44 PM Miguel Landaeta wrote: > > Thanks for the feedback. > > I attached a fixed version of the port. > > On Thu, Aug 3, 2023 at 11:04 PM Stuart Henderson wrote: > > > > Make sure that you can still produce a package if the 0.0 in &

Re: NEW: devel/py-icecream

2023-11-21 Thread Miguel Landaeta
On Thu, Nov 2, 2023 at 12:57 PM Miguel Landaeta wrote: > > [...] > > I attached a new revision addressing the comments above. > Ping. -- Miguel Landaeta, miguel at miguel.cc secure email with PGP 0x6E608B637D8967E9 available at http://keyserver.pgp.com/ "Faith means not

[MAINTAINER UPDATE] misc/libcpucycles (20230115 -> 20240114)

2024-02-04 Thread Miguel Landaeta
install.md: headings, note manual pages. - Add doc/license.md - Update HTML style for better tt visibility and copy-paste. Thanks! -- Miguel Landaeta, miguel at miguel.cc secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true

Re: update lang/mruby: install static libraries for embedding use case

2025-02-11 Thread Miguel Landaeta
On Fri, Jan 10, 2025 at 10:23:35AM +, Miguel Landaeta wrote: > Hi folks, 2nd ping for https://marc.info/?l=openbsd-ports&m=173650447718931&w=2 any comments? ok? Thanks! Miguel.

Re: update lang/mruby: install static libraries for embedding use case

2025-01-10 Thread Miguel Landaeta
On Fri, Jan 10, 2025 at 10:05:31AM +, Klemens Nanni wrote: > [...] > > These are files, so recursive cp is not needed. > Why not INSTALL_DATA? Makes sense, I was just being consistent with other commands used on the do-install target but it's more correct to use INSTALL_DATA as you suggest an

update lang/mruby: install static libraries for embedding use case

2025-01-09 Thread Miguel Landaeta
Hi, lang/mruby is an embeddable ruby interpreter, but currently is not supporting all use cases described in its official docs [1] because is not shipping libmruby.a static library. For reference, see also a typical linux package example shipping those files [2]. 1. https://mruby.org/docs/arti

update misc/libcpucycles (20230115 -> 20240318)

2025-01-08 Thread Miguel Landaeta
-REVISION= 0 MAINTAINER= Miguel Landaeta Index: distinfo === RCS file: /home/cvs/ports/misc/libcpucycles/distinfo,v diff -u -p -u -p -r1.1.1.1 distinfo --- distinfo14 Aug 2023 08:01:46 - 1.1.1.1 ++

Re: update misc/libcpucycles (20230115 -> 20240318)

2025-01-17 Thread Miguel Landaeta
On Wed, Jan 08, 2025 at 09:41:24PM +, Miguel Landaeta wrote: > There were a couple of upstream releases for libcpucycles > during 2024 and I think it makes sense to update the port. > > ok? ping See patch details at: https://marc.info/?l=openbsd-ports&m=173637324009333&a

Re: update lang/mruby: install static libraries for embedding use case

2025-01-17 Thread Miguel Landaeta
On Fri, Jan 10, 2025 at 10:23:35AM +, Miguel Landaeta wrote: > > Makes sense, I was just being consistent with other commands > used on the do-install target but it's more correct to use > INSTALL_DATA as you suggest and it's also consistent, I think. > >

Re: update misc/libcpucycles (20230115 -> 20240318)

2025-01-08 Thread Miguel Landaeta
On Wed, Jan 08, 2025 at 09:41:24PM +, Miguel Landaeta wrote: > There were a couple of upstream releases for libcpucycles > during 2024 and I think it makes sense to update the port. > > ok? It looks like my email client botched the diff, so I'm also attaching it to the thr