Opened 11 years ago

Closed 9 years ago

Last modified 9 years ago

#36959 closed update (fixed)

isync portfile update

Reported by: dave@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.1.2
Keywords: haspatch Cc: mww@…, neverpanic (Clemens Lang), nerdling (Jeremy Lavergne)
Port: isync

Description

Updates isync to 1.0.5, using db53, and provides a subport for a recent development snapshot

Attachments (2)

0001-Update-isync-portfile-to-include-isync-snapshot-and-.patch (2.9 KB) - added by dave@… 11 years ago.
Portfile.patch (1020 bytes) - added by dave@… 11 years ago.
Applied on top of previously-submitted patch, implements requested fixes

Download all attachments as: .zip

Change History (13)

comment:1 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Keywords: haspatch added
Type: submissionupdate

We use the "-devel" suffix for development versions, not "-snapshot". See #14540.

The dependency on p5-timedate must be changed to be on a specific perl version, such as p5.12-timedate. The software may also need to be patched to ensure that that version of perl gets used.

comment:2 Changed 11 years ago by dave@…

Huh; -devel in other contexts means "the package that supplies things developers need (like headers)". OK, I can fix that. Could you explain why the timedate dependency has to specify a particular version of Perl?

Changed 11 years ago by dave@…

Attachment: Portfile.patch added

Applied on top of previously-submitted patch, implements requested fixes

comment:3 in reply to:  2 Changed 11 years ago by jmroot (Joshua Root)

Replying to dave@…:

Could you explain why the timedate dependency has to specify a particular version of Perl?

p5-timedate depends on an arbitrary p5.x-timedate. ${prefix}/bin/perl points to an arbitrary version of perl. The two arbitrary versions are not guaranteed to be the same. You have to run a perl version that is known to have TimeDate installed.

comment:4 Changed 11 years ago by dave@…

Thanks. That seems like a deficiency in the expressivity of the language used to describe these dependencies. It should be possible to constrain them to the same version of Perl without nailing down the exact version. But again, thanks, I understand now.

comment:5 Changed 10 years ago by nerdling (Jeremy Lavergne)

Cc: cal@… snc@… added

There's an attempt to build 1.1.1 on the buildbots presently, and it succeeded on all but Snow Leopard:

WARNING: 'automake-1.14' is missing on your system.

https://build.macports.org/builders/buildports-snowleopard-x86_64/builds/27294

comment:6 Changed 9 years ago by neverpanic (Clemens Lang)

Resolution: fixed
Status: newclosed

I think most of this is implemented in r132620 and r132621.

comment:7 Changed 9 years ago by dave@…

Resolution: fixed
Status: closedreopened

It totally leaves out the snapshot subport, which was the main point of the ticket

comment:8 Changed 9 years ago by neverpanic (Clemens Lang)

Yes, but that's also the part I'm not going to implement, because I do not see a requirement for it. We do not have development snapshots for most other ports and our general policy is to package stable versions, especially when upstream actually does regular releases, which seems to be the case for mbsync.

Additionally, your original patch to add the devel subport is now several years out of date, and there already isn't anybody taking the time to maintain the isync port, lest anybody actually maintaining the -devel port and regularly updating that. I may soon step up to maintain isync, but I wouldn't maintain a devel subport. I'm inclined to treat this part of your ticket as "won't fix" unless there's a compelling reason not to.

comment:9 Changed 9 years ago by dave@…

Sounds good to me.

comment:10 Changed 9 years ago by neverpanic (Clemens Lang)

Resolution: fixed
Status: reopenedclosed

OK. Out of interest, what was your use case for the development snapshot?

comment:11 Changed 9 years ago by dave@…

It's hard to remember, but my guess is that I had contributed changes upstream and wanted to manage my installation with the isync port.

Note: See TracTickets for help on using tickets.