Re: [Fink-devel] Tiger grand design

2005-04-21 Thread Alexander K. Hansen
On Apr 18, 2005, at 8:43 PM, Chris Zubrzycki wrote:
Ok, here is my proposal, officially posted to the world. Users may not 
like it too much, but I honestly think it's the best way for us to 
handle it.

Users will have 2 choices:
a) reinstall fink from scratch
b) apt-get dist-upgrade
No other options will be supported officially. They can try to just 
update manually, but anything c++ will require patience to build in 
the correct order

We create bindists for both stable, and unstable, with package lists 
for users to review before upgrading, basically what builds under 
tiger and what does not. (IMO a stable tiger tree is an oxymoron at 
the moment, since we have 0 feedback on packages other than that they 
build, identical for unstable). ANY packages that do not build go back 
to experimental, and dummy placeholders are put into the bindist, so 
users cannot try to link against broken libs.

This will allow immediate upgrade, without the bother of a 
transitional tree. Any admin worth his salt will treat 10.4 as any new 
os; a major upgrade, and if the mission-critical software is not 
available yet, needs to wait to deploy. We will work as hard as we can 
to get everything built, Matt Sachs has been a giant help with that.

There is no time for any other solution, really, hopefully we can use 
Matt's build scripts as a start and then tweak it to be a full 
auto-build system. gpg-signed debs by the  main fink devs could be 
submitted and then mirrored, to help speed the process. Private seeds 
of GM would be wonderful from Apple (since we are already under NDA 
and i guess represent 100k+ mac machines)...I do not know if there 
will be subtle problems building on the last seeded release. If not, 
Matt might be able to get everything built in time, get us access to 
machines with tiger gm to build from.

-chris zubrzycki
- --
I think this could work out, provided that we make sure to put out an 
announcement that people who have "mission-critical" stuff may want to 
hold off on upgrading (which is generally true anyway).

From my experience dealing with users, it seems like there are many 
people who want to live on the bleeding-edge. and those that are more 
cautious tend not to upgrade their OS until the known issues are 
resolved.

--
Alexander K. Hansen
Associate Research Scientist, Columbia University
visiting MIT Plasma Science and Fusion Center
Levitated Dipole Experiment
175 Albany Street, NW17-219
Cambridge, MA  02139-4213

---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel


[Fink-devel] Tiger grand design

2005-04-18 Thread Chris Zubrzycki
Ok, here is my proposal, officially posted to the world. Users may  
not like it too much, but I honestly think it's the best way for us  
to handle it.

Users will have 2 choices:
a) reinstall fink from scratch
b) apt-get dist-upgrade
No other options will be supported officially. They can try to just  
update manually, but anything c++ will require patience to build in  
the correct order

We create bindists for both stable, and unstable, with package lists  
for users to review before upgrading, basically what builds under  
tiger and what does not. (IMO a stable tiger tree is an oxymoron at  
the moment, since we have 0 feedback on packages other than that they  
build, identical for unstable). ANY packages that do not build go  
back to experimental, and dummy placeholders are put into the  
bindist, so users cannot try to link against broken libs.

This will allow immediate upgrade, without the bother of a  
transitional tree. Any admin worth his salt will treat 10.4 as any  
new os; a major upgrade, and if the mission-critical software is not  
available yet, needs to wait to deploy. We will work as hard as we  
can to get everything built, Matt Sachs has been a giant help with that.

There is no time for any other solution, really, hopefully we can use  
Matt's build scripts as a start and then tweak it to be a full auto- 
build system. gpg-signed debs by the  main fink devs could be  
submitted and then mirrored, to help speed the process. Private seeds  
of GM would be wonderful from Apple (since we are already under NDA  
and i guess represent 100k+ mac machines)...I do not know if there  
will be subtle problems building on the last seeded release. If not,  
Matt might be able to get everything built in time, get us access to  
machines with tiger gm to build from.

-chris zubrzycki
- --
PGP public key: http://homepage.mac.com/beren/publickey.txt
ID: 0xA2ABC070
Fingerprint: 26B0 BA6B A409 FA83 42B3  1688 FBF9 8232 A2AB C070

Everyone who comes in here wants three things:
(1) They want it quick.
(2) They want it good.
(3) They want it cheap.
I tell 'em to pick two and call me back.
-- sign on the back wall of a small printing company

---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel