On Wednesday 26 November 2008 00:26, Florent Daigni?re wrote: > * Zero3 <zero3 at zerosplayground.dk> [2008-11-26 00:08:17]: > > > Matthew Toseland skrev: > > >> An > > >> installer that works on all three platforms has many advantages, but > > >> will never be as smooth or intuitive as platform-specific installers > > >> because people have differing expectations of each platform. For > > >> example, Windows users tend to expect a Wizard-style installer. Mac > > >> users expect a DMG containing an executable App that they can drag to > > >> their Applications folder. Linux users expect to be able to use > > >> apt-get, yum, or something else depending on their specific distro. > > >> > > > > > > Unless their specific distro happens to be unsupported. Which is common, > > > because the distro market is still extremely fragmented. Hence we need a good > > > GUI installer even for linux. No? > > > > > deb and rpm probably covers most of the GUI distros. The "Alien" program can convert packages to various other formats if needed. > > That's not proper packaging.
It should be possible to provide a .deb which is usable on all debian and ubuntu variants, no? I dunno whether we'll need a separate rpm for fedora vs suse. We already have a gentoo ebuild. > > > >> Next, we must identify anything that can be improved in Freenet that > > >> would make writing these installers easier. > > > > > > IMHO moving the "wizard" part into the node itself was an important step in > > > the right direction. We could move the rest into the node by always > > > downloading the plugins and seednodes file in the installer, and asking the > > > user about the plugins during the post-install wizard. Ideally we'd also ask > > > the user about auto-start in the post-install wizard (defaulting on but > > > executing a script to turn it off if the user asks us to). > > > > > I agree. It doesn't seem like that big of a task to move the rest of the > > stuff into the wizard (now you already have the framework). > > Putting stuffs in the wizard goes against the packaging logic. On debian > you would want to use debconf to ask the user on how to configure his > node... On Windows it makes sense, doesn't it? Well, mostly because we want to minimise the amount of Windows-specific code we maintain... ideally the installer would configure Freenet... -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20081126/0cc1678d/attachment.pgp>
