Hello ports@,

Here is a updated port of forgejo 7.0.9.

I attached the forgejo updated file.

This works on OpenBSD-7.6-beta amd64.

OK?

Purple Rain.


July 23, 2024 at 4:21 PM, "Igor Zornik" <mocheryl@mocheryl.org> wrote:
 
> Hello,
> 
> This still doesn't work because service account isn't set up. Attached
> is a PLIST I've taken and modified from gitea. I haven't tested it
> thoroughly, but with it you can at least run basic installation. Don't
> forget to add
> 
> 900 _forgejo _forgejo www/forgejo
> 
> to your `user.list` file.
> 
>> Might as well just write the manual directly to ${PREFIX}/man/man1/ in
>> post-install:, there's no need for the extra steps.
> 
> Oh, I see. Thanks for the tip. For some reason I thought you *had* to
> use "INSTALL_" commands to install things. That's why I unnecessarily
> complicated the process.
> 
> On 7/21/24 23:11, purplerain@secbsd.org wrote:
> 
>> Hello, I added the line for manual in post-install.
>> In other hand, according to the information from:
>> https://forgejo.org/compare-to-gitea/#why-must-i-keep-the-binary-name-gitea-on-upgrade
>> Since this requirement is only for updating from an existing Gitea installation.
>> It is not for a fresh Forgejo installation.
>> Should I still add the symbolic link? If the answer is yes,
>> where should pointed the symbolic link?
>> Thank you for your comments, they are very valuable.
>> I attached the forgejo updated file.
>> Purple Rain.
>> July 14, 2024 at 4:01 AM, "Stuart Henderson" <stu@spacehopper.org> wrote:
>>>> Might as well just write the manual directly to ${PREFIX}/man/man1/ in post-install:, there's no
>>> need for the extra steps.
>>> 
>>> --
>>> 
>>> Sent from a phone, apologies for poor formatting.
>>> 
>>> On 14 July 2024 08:25:08 Igor Zornik <mocheryl@mocheryl.org> wrote:
>> 
>> Hello,
>> 
>> A few points I would like to make.
>> 
>> This port doesn’t work as-is because it fails to account for the new
>> 
>> daemon user. You must add appropriate entries to PLIST for that.
>> 
>> Is there a reason we couldn’t use the single-binary build mode? The
>> 
>> distribution already includes all the generated files which is great
>> 
>> because no extra work is needed. Just including “bindata” into tags
>> 
>> seems to work.
>> 
>> Here’s also a little trick to get the man page. Add a post-build event
>> 
>> where we write the file:
>> 
>> post-build:
>> @mkdir -p ${WRKSRC}/man/man1
>> ${MODGO_WORKSPACE}/bin/gitea docs --man > ${WRKSRC}/man/man1/forgejo.1
>> 
>> Then move it in the post install event:
>> 
>> ${INSTALL_MAN} ${WRKSRC}/man/man1/forgejo.1 ${PREFIX}/man/man1/
>> 
>> On 7/5/24 10:07, Purple Rain wrote:
>> 
>> Hello ports@,
>> 
>> Here is a new port www/forgejo 7.0.5.
>> 
>> Forgejo is a self-hosted lightweight version control software.
>> A hard fork of Gitea. Forgejo is built to be privacy first.
>> 
>> The difference between Forgejo and Gitea:
>> https://forgejo.org/compare-to-gitea
>> 
>> This works OK on OpenBSD-7.5-current amd64.
>> 
>> OK?
>> 
>> Purple Rain.

• forgejo.tgz (19K)