Opened 4 years ago

Closed 4 years ago

#52542 closed submission (wontfix)

widelands-devel -- build from the latest revision of the bzr source tree

Reported by: ken-cunningham-webuse Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: Cc: ryandesign (Ryan Schmidt)
Port: widelands-devel

Description

For your testing and interest, this port file builds the latest bzr version of widelands, currently a feature-frozen 1.9 version. Once the final 1.9 version is committed to tarball, this port file will change to that version.

The widelands developers are hoping for feedback on this feature-frozen version prior to the release of 1.9.

In my testing so far, this version works well on 10.11, but as of 20161007, segfaults on 10.6.

Attachments (3)

Portfile (3.3 KB) - added by ken-cunningham-webuse 4 years ago.
widelands-devel Portfile 1.9 v2 (2.6 KB) - added by ken-cunningham-webuse 4 years ago.
portfile widelands-devel (1.9 r 8119 at present)
widelands-devel Portfile 1.9 v3 (2.6 KB) - added by ken-cunningham-webuse 4 years ago.
update to r8131 from the dev tree (latest)

Download all attachments as: .zip

Change History (10)

Changed 4 years ago by ken-cunningham-webuse

Attachment: Portfile added

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

Cc: ryandesign@… added

I don't see where in this Portfile it instructs Bazaar which revision or commit or tag of the repository to download. That's required. See ReproducibleBuilds#Fetchingthesourcefromarepository.

Did you consider making this a subport of the widelands port, since it has much in common with it? It might be simpler to wait until after #52188 is resolved so we don't duplicate effort.

comment:2 Changed 4 years ago by ken-cunningham-webuse

I made this one for the tip of the dev tree -- latest revision. I was aware of the reproducible builds wiki -- but would this approach not be better for a dev build? For a devel-build that they are looking for feedback on, this seemed appropriate. The code will change nightly, but that's what the devs want feedback on.

Also -- help me out here if you can -- for the life of me I couldn't find my way through the bazaar source tree website to find a specific revision for widelands I can peg to, like I can for git or have done for a number of others. I know it is possible to specify a revision - their website says it is possible -- but yuck- it's buried in there somewhere deep enough that I couldn't stumble across it after an hour !! Have you been down that road before with bazaar??

Maybe you have to do it manually using the command-line tools and find a specific rev that way? Or maybe I didn't notice the right

comment:3 in reply to:  2 Changed 4 years ago by ryandesign (Ryan Schmidt)

Replying to ken.cunningham.webuse@…:

I made this one for the tip of the dev tree -- latest revision. I was aware of the reproducible builds wiki -- but would this approach not be better for a dev build? For a devel-build that they are looking for feedback on, this seemed appropriate. The code will change nightly, but that's what the devs want feedback on.

The wiki page explains the many reasons why this doesn't work for MacPorts. You must specify a revision. If they update the source, you can update the source revision in the portfile, and increase the version field so that users will know a change was made.

Also -- help me out here if you can -- for the life of me I couldn't find my way through the bazaar source tree website to find a specific revision for widelands I can peg to, like I can for git or have done for a number of others. I know it is possible to specify a revision - their website says it is possible -- but yuck- it's buried in there somewhere deep enough that I couldn't stumble across it after an hour !! Have you been down that road before with bazaar??

Maybe you have to do it manually using the command-line tools and find a specific rev that way? Or maybe I didn't notice the right

Unfortunately I can't help here; I haven't used Bazaar.

comment:4 Changed 4 years ago by ken-cunningham-webuse

I finally found a rev number for the current developer build of 1.9 in the README, of all places. Whew! New portfile attached.

Re: a subport. Well first thing is I don't know exactly how to do that yet :> But to bolster the idea of a separate portfile, the supporting ports were all changed to libsdl2, the fetch mechanism changed, and the file path for the icns file was altered, so there are a fair few changes from 1.8. Have a look and see what you think. If you feel a subport is the way to go, I'll be happy to look into that further. -- K

Changed 4 years ago by ken-cunningham-webuse

portfile widelands-devel (1.9 r 8119 at present)

Changed 4 years ago by ken-cunningham-webuse

update to r8131 from the dev tree (latest)

comment:5 Changed 4 years ago by ken-cunningham-webuse

Hello friendly port maintainers. I think this portfile should be good to use for anyone who is wanting a recent widelands development version to test and use to give feedback to the widelands developers. Please consider for committing as widelands-devel. Once the final version of widelands 1.9 is released, I'll update the widelands port to that version using this as a template. -- K

comment:6 Changed 4 years ago by ken-cunningham-webuse

OK. Please don't commit this port now, as build19 has been released, and the widelands port has been updated to that version. You might as well close this ticket off with a "wontfix".

comment:7 Changed 4 years ago by mf2k (Frank Schima)

Resolution: wontfix
Status: newclosed
Note: See TracTickets for help on using tickets.