From: Manolis Ragkousis <manolis837@gmail.com>
To: Alex Kost <alezost@gmail.com>
Cc: 27235@debbugs.gnu.org
Subject: bug#27235: [PATCH] gnu: Add openscenegraph.
Date: Wed, 7 Jun 2017 09:29:26 +0300 [thread overview]
Message-ID: <4145b1ee-5ad9-a56f-1165-89e2b85f7fdc@gmail.com> (raw)
In-Reply-To: <87vao8anw6.fsf@gmail.com>
Hey Alex,
On 06/06/17 22:59, Alex Kost wrote:
> manolis837@gmail.com (2017-06-04 17:57 +0300) wrote:
>
>> +(define-public openscenegraph
>> + (package
>> + (name "openscenegraph")
>> + (version "3.4.0")
>> + (source (origin
>> + (method url-fetch)
>> + (uri (string-append "http://trac.openscenegraph.org/downloads/developer_releases/"
>> + "OpenSceneGraph-" version ".zip"))
>
> Isn't this version old? I see 3.5.6 here:
>
> https://github.com/openscenegraph/OpenSceneGraph/releases
>
I was following this [1] and chose 3.4.0.
The github release is a developer version and according to [2]: "Our
developer releases are made more regularily than our stable releases and
are simply tags of the latest source code under version control. The
developer releases do not under any dedicated testing prior to release
and are meant to be snapshots of the latest development work that is
going into the next stable release. The versioning for stable release is
major.minor.patch where the minor release is odd number signifying that
it's developer release."
For this reason I think we should go with 3.4.0 for now.
Thank you,
Manolis
[1] http://www.openscenegraph.org/index.php/download-section/stable-releases
[2]
http://www.openscenegraph.org/index.php/download-section/developer-releases
next prev parent reply other threads:[~2017-06-07 6:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-04 14:57 bug#27235: [PATCH] gnu: Add openscenegraph manolis837
2017-06-04 17:45 ` Leo Famulari
2017-06-04 19:00 ` Manolis Ragkousis
2017-06-06 19:59 ` Alex Kost
2017-06-07 6:29 ` Manolis Ragkousis [this message]
2017-06-07 9:47 ` Alex Kost
2017-06-07 10:05 ` Manolis Ragkousis
2017-06-07 19:54 ` Alex Kost
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4145b1ee-5ad9-a56f-1165-89e2b85f7fdc@gmail.com \
--to=manolis837@gmail.com \
--cc=27235@debbugs.gnu.org \
--cc=alezost@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.