Bug 230769 - [NEW PORT] ports-mgmt/caronte: easy port and binary packages updater
Summary: [NEW PORT] ports-mgmt/caronte: easy port and binary packages updater
Status: Closed Not A Bug
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:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-20 10:02 UTC by Lorenzo Salvadore
Modified: 2019-01-20 22:49 UTC (History)
1 user (show)

See Also:


Attachments
Shar file of the new port. (2.55 KB, text/plain)
2018-08-20 10:02 UTC, Lorenzo Salvadore
no flags Details
Second shar file of the port (2.55 KB, text/plain)
2018-08-23 10:17 UTC, Lorenzo Salvadore
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lorenzo Salvadore freebsd_committer freebsd_triage 2018-08-20 10:02:14 UTC
Created attachment 196379 [details]
Shar file of the new port.

Easy port and binary packages updater.
Comment 1 Nathan 2018-08-21 17:25:49 UTC
Getting errors 
Facility=user: Command not found.                  
TagLog=caronte: Command not found.                 ConfigurationFile=/usr/local/etc/caronte.conf: Command not found.

Also says portsnap is not found which would need to be added as a run rep if it relies on portsnap
Comment 2 Lorenzo Salvadore freebsd_committer freebsd_triage 2018-08-22 19:47:58 UTC
I am working on fixing these errors: can you please tell me how did you get them? I tested the port with portlint, porttools, poudriere and have not got any of them: if I could reproduce them myself I could avoid waisting your time with patches that do not fix the problem.

As for portsnap, I thought it is in the base system and did not need to be listed as a dependency: am I wrong? And does it mean that other tools such as sh and pkg must be listed too?

Thanks.
Comment 3 Lorenzo Salvadore freebsd_committer freebsd_triage 2018-08-22 21:21:01 UTC
(In reply to Lorenzo Salvadore from comment #2)

I found how to reproduce the errors. The problem was in the kind of shell used to test Caronte: because of a typo in the shabang of Caronte's script (missing "!"), shells such as tcsh were unable to execute correctly the script. As Caronte's author I could easily fix the typo.

The first errors have thus been corrected, however some new ones have appeared: I will post a new shar file only when everything will work fine.

I refrain from adding run dependencies until your confirmation that they are needed (I would not even know how to add a portsnap dependency: it seems it is even missing from my port tree).
Comment 4 Nathan 2018-08-22 22:35:51 UTC
(In reply to Lorenzo Salvadore from comment #3)

Hmm it is PROBABLY in base, I tested this in poudriere, and it seems doesn't have portsnap in it
Comment 5 Lorenzo Salvadore freebsd_committer freebsd_triage 2018-08-23 10:17:09 UTC
Created attachment 196471 [details]
Second shar file of the port
Comment 6 Lorenzo Salvadore freebsd_committer freebsd_triage 2018-08-23 10:22:24 UTC
(In reply to Lorenzo Salvadore from comment #5)

I tried to add a portsnap run dependency with "RUN_DEPENDS= portsnap:ports-mgmt/portsnap" but it did not work because the port does not exist. The ouput of "make search name=portsnap" states "Part of the base system since FreeBSD 5.5".
Comment 7 Lorenzo Salvadore freebsd_committer freebsd_triage 2018-08-24 21:46:16 UTC
(In reply to Lorenzo Salvadore from comment #6)

I have tested again with poudriere and I confirm that it has portsnap without specifying any dependency (tested on a FreeBSD version 11.2-RELEASE). The attachement "Second shar file of the port" should then work without troubles.

I think the message that suggested you that portsnap was missing was only a consequence of the typo in the shabang.
Comment 8 Lorenzo Salvadore freebsd_committer freebsd_triage 2019-01-20 22:49:18 UTC
I changed my mind about this port, I am unsure there really is a need for such a port in the ports tree. I might try again to include it in the future, in case I improve the software, but at the moment I think it is better to discard it.