Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
pure-lang
Home
+ new post
About this group
Join this group
Message from discussion ANN: Pure 0.48
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Ryan Schmidt  
View profile  
 More options Oct 20 2011, 4:47 pm
From: Ryan Schmidt <google-2...@ryandesign.com>
Date: Thu, 20 Oct 2011 15:47:26 -0500
Local: Thurs, Oct 20 2011 4:47 pm
Subject: Re: [pure-lang] ANN: Pure 0.48
Print | View thread | Show original | Report this message | Find messages by this author
On Oct 20, 2011, at 04:31, Albert Graef wrote:

> On 10/20/2011 08:44 AM, Ryan Schmidt wrote:
>> I'm working on getting the pure 0.48 update into MacPorts.

> Thanks!

> A quick heads up (also for the other package maintainers). I'm currently rolling new tarballs with fixed up READMEs (i.e., expanded @version@ and |today| tags) for *all* packages. This is only for the latest release of each package, and serves purely cosmetic purposes. You might just ignore these as there are no code changes whatsoever, but for those of you who are building source packages (source debs, rpms, whatever) which contain the upstream sources, it may be advisable to just wait with rolling and uploading your packages until I'm finished with this (shouldn't take more than an hour or so).

> Ryan, this probably won't affect you, unless MacPorts also keeps their own copies of the upstream tarballs somewhere.

It does affect MacPorts, both in that we do have a network of servers [1] that automatically mirror tarballs when we commit updated portfiles, and in that we record checksums of each tarball in each portfile, and if upstream changes it, we'll have to update and re-test the portfiles. We call this a "stealth update" [2]. It's not a problem in this particular instance since I haven't committed the 0.48 update yet but in general we would love it if developers wouldn't do stealth updates. :)

[1] https://trac.macports.org/wiki/Mirrors#Distfiles

[2] https://trac.macports.org/wiki/PortfileRecipes#stealth-updates


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google