Bug 268529 - www/surfraw: Revive
Summary: www/surfraw: Revive
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL: https://gitlab.com/surfraw/Surfraw
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-23 19:38 UTC by Oleh Vinichenko
Modified: 2022-12-24 09:21 UTC (History)
2 users (show)

See Also:

Attachments
revive 44db0fd (10.57 KB, patch)
2022-12-23 20:04 UTC, Nuno Teixeira 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Oleh Vinichenko 2022-12-23 19:38:09 UTC 
According to freshports status, www/surfraw is flagged broken, unfetchable [1].
It is available on https://gitlab.com/surfraw/Surfraw and tarball for latest version, 2.3.0, can be obtained from:
https://gitlab.com/surfraw/Surfraw/-/archive/surfraw-2.3.0/surfraw-2.3.0.tar.bz2
Currently, i am not able to provide diff to removed port with updated distfiles entries.
[1]: https://www.freshports.org/www/surfraw/
Comment 1 Nuno Teixeira freebsd_committer freebsd_triage 2022-12-23 20:04:00 UTC 
Created attachment 238989 [details]
revive 44db0fd

revert from 44db0fd:

---
commit 44db0fdc07ab8389818782fde4f3d3d367980a76
Author: Philippe Audeoud <jadawin@FreeBSD.org>
Date:   Thu Jun 4 06:53:43 2015 +0000

    - Fix shebangs
    - Don't install config files without .sample suffix, these are handled by pkg
    - Remove MLINKS, unneeded with pkg
    - Use @sample
    - Remove @dirrm* from plist

    PR:             200038
    Submitted by:   amdmi3@
---

There are missing files.
Comment 2 Nuno Teixeira freebsd_committer freebsd_triage 2022-12-23 20:05:49 UTC 
(In reply to Oleh Vinichenko from comment #0)

2.3.0 is 4 years old, are you sure that project is still alive?
Comment 3 Oleh Vinichenko 2022-12-23 21:02:07 UTC 
i have seen activity on project gitlab page, so only thing i can judge from that that project is not dead. for as long as it can be fetched, compiled and working, i will be happy. Alternatively, a snapshot tarball can be used? latest changes are 1 year old, so it is "newer". i do not know what is a policy about it.
Comment 4 Nuno Teixeira freebsd_committer freebsd_triage 2022-12-23 21:12:22 UTC 
(In reply to Oleh Vinichenko from comment #3)

Yes, snapshot tags/tarball can be used.
Comment 5 Li-Wen Hsu freebsd_committer freebsd_triage 2022-12-24 07:26:03 UTC 
(In reply to Oleh Vinichenko from comment #3)
We also need to find a MAINTAINER of the revived port, are you willing to do it?
Comment 6 Oleh Vinichenko 2022-12-24 09:21:48 UTC 
i would like to, but, firstly,  i am yet unfamiliar with ports framework, only rudimentary understanding about it. secondly, there is very unstable situation here and the reason for this software is to avoid using browsers to save battery life.