[hxclidev] Re: [dna-dev] Re: [hxclidev] Re: Installer for Helix Player?
Dean Collins dcollins at real.comOn Thu, Jul 24, 2003 at 10:29:16AM -0700, Haydon Boone wrote: > My vote is that the default should be an executable graphical > installer/uninstaller, with distro-specific rpms created as > needed/justified/requested. > > As we learned from the Unix RP7/RP8/ROP Alpha products, there will > always be a portion of the user base who complains about "the stoopid > graphical UI, what a waste of time, give me a command line installer you > GUI dorks" but there will also be a significant, mostly-silent, portion of > the user base who you don't hear from because the installer "just works", > doing what it's supposed to w/out confusion, allowing them to easily get to > the point of the exercise - actually using the product. > > Also, provide an option to allow the installer to be kicked off from the > command line with a bunch of name-value pairs to allow total installation & > configuration without any user prompts (other than "Install Complete" or > "Error:", of course) - enterprise users will thank you. The server's installer provides this capability, btw. > > At 04:29 AM 7/24/2003, Greg Wright wrote: > >I think a executable installer is nice to have. Lets also not forget a > >uninstaller as well (at least a readme with all the file locations). > > > >However, it should not be too hard to have packages for some of the > >more popular systems like RedHat and Debian. > > > >--greg > > > > > >From: "Vikram Dendi" <vikram at helixcommunity.org> > > > What sort of an installer should the Helix Player for Linux support? > > > > > > Should it just be a package such as rpm (with maybe post-install scripts > > > to register filetypes and such), or should we ALSO offer a full-fledged > > > installer (graphical?) like Ximian's? > > > > > > One suggestion was to look at the Server installer here: > > > https://server.helixcommunity.org/source/browse/server/installer/ > > > What would be the benefits of having such an installer? > > > > > > Along the custom installer lines, what about doing it like rp8 does it? > > > (download bin and run). If NOT being able to tell the rpm database about > > > it being installed is an issue - we could get the installer/executable > > > to update the database on first run. This way the user has a choice on > > > how to upgrade/uninstall in the future. A good graphical installer also > > > is useful when we port to systems that don't have package management. > > > > > > Please share your thoughts. Join the Helix Player project! :-) > > > -V > > > > > > https://player.helixcommunity.org/servlets/ProjectMailingListList > > > > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: dev-unsubscribe at helix-client.helixcommunity.org > >For additional commands, e-mail: dev-help at helix-client.helixcommunity.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe at helix-dna.helixcommunity.org > For additional commands, e-mail: dev-help at helix-dna.helixcommunity.org > -- Dean Collins Server Technical Lead, RealNetworks, Inc. -- http://www.realnetworks.com Helix Server Project Owner -- http://helix-server.helixcommunity.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe at helix-client.helixcommunity.org For additional commands, e-mail: dev-help at helix-client.helixcommunity.org