Re: Nuking the Cygwin packaging for 'chere'
Mark Geisert via Cygwin-apps <[email protected]>
| Newsgroups | gmane.os.cygwin.applications |
|---|---|
| Message-ID | <[email protected]> |
On 8/27/2025 8:43 AM, Jon Turney via Cygwin-apps wrote:
> On 27/08/2025 16:37, Jon Turney wrote:
>> On 27/08/2025 05:30, Mark Geisert via Cygwin-apps wrote:
>>> By mistake I replicated the author's git repository of chere into the
>>> Cygwin repository. How can I nuke that so I can push my own repo,
>>> which just has a .cygport and patch file like most projects have?
>
> If I might gently suggest to start as you hope to go on, there should
> never be a need for a patch file for a package where you are the upstream.
>
>
> You can strip back the chere Makefile to something like:
>
>> .PHONY=all install
>>
>> BIN_IPATH:=usr/bin
>> MAN_IPATH:=usr/share/man/man1
>>
>> all :
>>
>> install :
>> mkdir -p $(DESTDIR)/$(BIN_IPATH)
>> cp src/chere $(DESTDIR)/$(BIN_IPATH)/chere
>> cp src/xhere $(DESTDIR)/$(BIN_IPATH)/xhere
>> mkdir -p $(DESTDIR)/$(MAN_IPATH)
>> gzip -c src/chere.1 > $(DESTDIR)/$(MAN_IPATH)/chere.1.gz
>>
>
> Then stick a tag on it.
>
> Then the cygport should be relatively straightforward:
>
>> NAME="chere"
>> VERSION=1.5
>> RELEASE=1
>>
>> SUMMARY="Cygwin Prompt Here context menus"
>> DESCRIPTION="Shell script to manage shell here context menus for Cygwin"
>> HOMEPAGE="https://cygwin.com/cgit/cygwin-apps/chere/"
>> LICENSE="Public-Domain"
>>
>> CATEGORY="Shells Utils System"
>> REQUIRES="cygwin coreutils run getent"
>>
>> GIT_URI="git://cygwin.com/git/cygwin-apps/chere"
>> GIT_TAG="${VERSION//\./_}"
>> inherit git
>>
>> src_compile() {
>> :
>> }
>>
>> src_install() {
>> cd ${S}
>> cyginstall
>> }
>
> Modify the tagging style and transformation to your taste.
>
> The choice license is based on the statement in the manpage. A brief
> look at the mailing list history when this package was first created
> unfortunately doesn't shed any more light.
Thanks very much for this input, Jon, and for the cleanup work you've
done on my chere repo. I will proceed down this path when I return to
the land of keyboards in a couple weeks. At that time I will also
address the missing commits in my cygutils git repo.
Cheers & Regards,
..mark