Re: [24915] branches/release_1_4/base
On May 8, 2007, at 1:11 AM, source_changes@macosforge.org wrote:
Also, moving the IndexRegen.sh script to check out from the tags dir, thus keeping the checkout always in sync with the latest MacPorts release. NOTE to dluke: You should probably reinstall this script and bootstrap it again ;-)
This change won't actually work the way you want it to. Currently, I manually move a copy of IndexRegen.sh into position to actually run on my machine (as I don't particularly want anyone with commit access to be able to run arbitrary shell scripts on my machine (although it's probably a mute point as anyone with commit access could modify any of the base/ code that gets executed just as easily)). SVN_BASE_URL isn't actually used by the script for much more than documentation, so changing it wont change where the checkout happens. The script pulls from the latest release branch, and therefore doesn't need intervention unless/until major releases (when I would manually switch the repo to the later branch). Changing to a tag would require manual intervention on my part for every release. In fact, I would rather we went in the opposite direction, where there was a 'current-release' branch that was used for the index regen. -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
On May 8, 2007, at 1:32 PM, Daniel J. Luke wrote:
On May 8, 2007, at 1:11 AM, source_changes@macosforge.org wrote:
Also, moving the IndexRegen.sh script to check out from the tags dir, thus keeping the checkout always in sync with the latest MacPorts release. NOTE to dluke: You should probably reinstall this script and bootstrap it again ;-)
This change won't actually work the way you want it to.
Currently, I manually move a copy of IndexRegen.sh into position to actually run on my machine (as I don't particularly want anyone with commit access to be able to run arbitrary shell scripts on my machine (although it's probably a mute point as anyone with commit access could modify any of the base/ code that gets executed just as easily)).
I understand taking precautions ;-)
SVN_BASE_URL isn't actually used by the script for much more than documentation, so changing it wont change where the checkout happens.
Yeah, the script does not bootstrap the checkout, but only updates it (therefore, the checkout could happen from any URL, initially). In any case, I only meant updating the variable for documentation purposes too, to reflect what release we're indexing with. All this is, arguably, largely unnecessary, so we shouldn't be too stringent as long as it's always clear what release the script tracks (therefore, update from the current release branch, from a tag... doesn't make much difference as long as the intent is clear).
The script pulls from the latest release branch, and therefore doesn't need intervention unless/until major releases (when I would manually switch the repo to the later branch). Changing to a tag would require manual intervention on my part for every release.
I understand wanting to minimize maintenance, so lets keep it pointing to the branch then.
In fact, I would rather we went in the opposite direction, where there was a 'current-release' branch that was used for the index regen.
Not sure what you mean by this.... what we just coincided on above...? Or are you referring to some alternate approach? -jmpp
-- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
On May 8, 2007, at 4:40 PM, Juan Manuel Palacios wrote:
Not sure what you mean by this.... what we just coincided on above...? Or are you referring to some alternate approach?
So, right now there are a bunch of tags for releases, and then branches for major releases. If there were yet-another branch that was always pointed to the current release, we could just point the script there. I don't want to make more work for someone else, though. -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
On May 8, 2007, at 1:44 PM, Daniel J. Luke wrote:
On May 8, 2007, at 4:40 PM, Juan Manuel Palacios wrote:
Not sure what you mean by this.... what we just coincided on above...? Or are you referring to some alternate approach?
So, right now there are a bunch of tags for releases, and then branches for major releases. If there were yet-another branch that was always pointed to the current release, we could just point the script there.
I don't want to make more work for someone else, though.
I'd love it if we just used the same approach as the rsync script (http://trac.macports.org/projects/macports/browser/trunk/base/ portmgr/mprsyncup) does: just checkout the RELEASE_URL file from trunk, and use its contents as the url to checkout from. This way the RELEASE_URL file is the only discriminator of what's current. Does that work? James
-- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev
On May 8, 2007, at 4:54 PM, James Berry wrote:
Does that work?
Yep. I'll work on enhancing the script tonight/tomorrow unless someone else wants to ;-) -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
On May 8, 2007, at 4:58 PM, Daniel J. Luke wrote:
I'll work on enhancing the script tonight/tomorrow unless someone else wants to ;-)
As a follow-up, this is done. The updated script is running on the index regen machine and checked in. -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
Hey, Thanks Daniel! You might be able to save a bit of time/bandwidth by doing an explicit checkout for just that one file (RELEASE_URL) you need from trunk. But the important thing is that it's working and running now ;) Thanks again. James On May 9, 2007, at 7:35 AM, Daniel J.Luke wrote:
On May 8, 2007, at 4:58 PM, Daniel J. Luke wrote:
I'll work on enhancing the script tonight/tomorrow unless someone else wants to ;-)
As a follow-up, this is done. The updated script is running on the index regen machine and checked in. -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
participants (4)
-
Daniel J. Luke
-
Daniel J.Luke
-
James Berry
-
Juan Manuel Palacios