helloSystem hello conflict with misc/hello

Graham Perrin grahamperrin at gmail.com
Sat Mar 6 14:37:07 UTC 2021


Hi, my first post to this list.

I'm neither a porter nor a developer, however a FreeBSD-oriented project 
will benefit from your advice. Briefly:

1. when the manifest for 'hello' was created 
<https://github.com/helloSystem/ISO/blob/f41e37266cec4377221e8e7742f9a9bb15285fd5/overlays/uzip/hello/manifest> 
the conflict with misc/hello was not foreseen

2. need to resolve the conflict **and** continue to have helloSystem 
recognisable as such for the purpose of 
<https://bsd-hardware.info/?d=helloSystem>.

A little more detail, my perspective: 
<https://gist.github.com/grahamperrin/6ae91f3cb559c7cd65f04cee1be13159#exceptions-for-users-of-hellosystem>

<https://pastebin.com/fbZCCQ0z> presents package info for the latest 
release <https://github.com/helloSystem/ISO/releases/tag/r0.4.0>.


### Background

Linux Hardware Project commit 
<https://github.com/linuxhw/hw-probe/commit/e71dba9f9a4cfda9fb4255bbdf1c1e8b3a7c8d2d> 
(2021-01-03) added support for helloSystem.

<https://github.com/helloSystem/hello/issues/67#issuecomment-753611844> 
was the corresponding point in time in the helloSystem issue through 
which a method of support was initially agreed. This issue was closed, 
then reopened in light of the naming conflict.

(Related <https://github.com/helloSystem/ISO/issues/14> is a potentially 
confusing mash of different issues. I view the cessation of support for 
`pkg update`, `pkg upgrade` and `freebsd-update` – and subsequent 
replacement of /usr/sbin/pkg – as unfortunate consequences of gaps in 
understanding, there and elsewhere … but I digress.)

Refocusing on the naming conflict: I look forward to your advice; either 
here, or under 
<https://github.com/helloSystem/hello/issues/67#issuecomment-772307831>.

Thanks
Graham


More information about the freebsd-ports mailing list