Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#7238 closed defect (fixed)

MultiTail is out of date

Reported by: luc@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.2
Keywords: Cc: olegb@…, gcomnz@…, markd@…
Port:

Description

Current Portfile is at 3.0.6, current stable version is at 3.8.5 :) The attached patch updates to latest stable and fixes a problem when installing the configuration file.

Attachments (1)

Portfile.patch (785 bytes) - added by luc@… 15 years ago.
Portfile patch for multitail 3.8.5

Download all attachments as: .zip

Change History (9)

Changed 15 years ago by luc@…

Attachment: Portfile.patch added

Portfile patch for multitail 3.8.5

comment:1 Changed 15 years ago by olegb@…

Cc: olegb@… gcomnz@… added

What does the maintainer say ?

comment:2 Changed 15 years ago by luc@…

FYI, multitail just went 3.8.6... :)

comment:3 Changed 15 years ago by markd@…

Cc: markd@… added
Resolution: fixed
Status: newclosed

(In reply to comment #3)

FYI, multitail just went 3.8.6... :)

Maintainer not responsive right now. Patch looks good so I just committed v3.8.9.1, latest stable one. Thanks Luc! Do you have any interest in being maintainer for this port if the current maintainer ok's it or never responds?

comment:4 Changed 15 years ago by luc@…

Sure, thanks for proposing. How does it work ?

comment:5 Changed 15 years ago by markd@…

(In reply to comment #5)

Sure, thanks for proposing. How does it work ?

Your email address just gets listed in the port, so you become a point of contact. It's generally isn't a burden, at least not if the app is "low maintenace" as it appears to me multitail is. I've been maintainer for ports that have never had a bug filed against them. But if/when someone does, or when you see updates to the app (you aren't obligated to search for them but if you use the app and check once in awhile anyway ...) you can test a port update on your local port and just say "yeah it works" or "this version now needs configured with --disable-dooda" so we can commit it. If you need help you can always ask the list. You reported it anyway, but the process is held up because the maintainer may have moved on. If you are interested let me know and I'd just add you after doing a "port abandoned" procedure and assuming that the current maintainer doesn't answer and say he still wants to maintain.

comment:6 Changed 15 years ago by luc@…

This sound like a good way for me to finally start to get involved in some way. Count me in.

comment:7 Changed 15 years ago by luc@…

FYI, multitail is now at 4.0.0... :)

Mark ? What does tha maintainer say ?

comment:8 Changed 15 years ago by markd@…

(In reply to comment #8)

FYI, multitail is now at 4.0.0... :)

Mark ? What does tha maintainer say ?

That app is a fast moving target. Maintainer never answered. Thanks for stepping up! I just commited the update to 4.0.0 and listed your email address as the maintainer. Let me know if there are any problems with update. Next time you see an update just file a new bug and put UPDATE multitail-4.0.0 -> 4.0.x. You could attach a patch file to make it a little easier for the committer if you want. Email me offline if you are interested in knowing how to make patch files. It is not hard.

Note: See TracTickets for help on using tickets.