Auteur
geit
geit
Forum » » Développement » » Grunch ou vos prochaines mises à jour faciles
Post� : 22-07-2011 12:30 
Ok, I read the stuff above and it seem I need to clarify a lot
First, I am not stupid and I saw the failures before, trying to set-up a working
packet manager system which is accepted by the people and by the developers.
That's why I usually do a brainstorming about what I need and what I want. Yes, I
am selfish here, because if I do not need something its boring to program it.
That's work and I want a little fun. Back to the topic.
I came up with a list why those other systems failed:
1. Servers
Servers are a good thing, but can be a pain in the ass if they are not or no
longer available.
2. Support by the developers
Developers needed to support a packet manager or software was not be able to be
used with the manager.
3. Repacking
It was always needed to repack the software which made it complicated.
Those three points killed those projects, even before you look at the software
itself, which may been great. I did not look at it ether.
So what is my solution? Well, Server are good, but should be easy to replace.
Support by the developers is good, but if he does not care about the project it
should be fine, too. And no repacking!
Stupid? Only on the first look I inverted the first points from good to bad.
Lets start with the second one. Its not bad to have developers supporting such
Software, as long as they like to. It is help. Speaking about help. There are
hundreds of people out there able to maintain their system by hand. Why not
allow them to participate to help?
This is the big goal. Everyone can help. Back to the servers. Servers in this
case are simple http servers. Nothing special, but centralized enough to feed
the masses out there with new data files.
Some people are translators and love to fix and update catalogs, while other
love to use them. A database file on a server and zwoosh. Quick interaction
without any need of placing the files inside a global database.
Yomgui mentioned the maintaining of the database. Or in other words: What
happens when geit sits dead in his chair? The solution would be easy. Someone
would take the latest database change the URL inside to his webpage and uploads
it. The users now are able to download the file once and place it into their
Grunch drawer. From now own the database is under control of that new guy.
Simple isn't it?
Speaking about the database and the time needed to update by the non dead
maintainer. Everyone is able to set up a server (its a file on a webserver, can
even be an Aminet text upload) for his own needs. If a developer wants to ensure
the installation is done as it was meant by him, he provides a self updating
database on his pages. The user can download the file, place it into his Grunch
database folder and from now Grunch updates stuff from that developer direct.
Well, I talked about updating a lot and you may say "yeah its a packet manager".
It is not!
It's more than that. People talked about setting up an AppStore for MorphOS or
AmigaOS. Well, there was much laughter, but frankly its nice to have a central
point, where you search for software and a click later it is installed. (iPad
user speaking). This thing is a more flexible way than Papiosaur's Pack
Ultimate. The pack is nice and helpful for new people, but it contains so much
nice software which cannot be seen by people already have there set-up system.
And yes I did not install the pack, but downloaded it to simply drag over the
stuff I needed. Grunch is (will be) kind a software store where you search for
stuff and install it or if you want to uninstall, that can be done, too. Today I
got noticed about the OWB update by Grunch and a single click later it was
installed. Even that click can be avoided by disabling update requests, as you
can see on the image above in papiosaur´s post.
It's also connected to Magic Beacon, which means you´ll get notified on updates
and updates get downloaded automagically if you like. So even if you want install
by your self this tool is nice to have.
Tcheko mentioned the dependency problem. This is a real problem not only on
MorphOS. Grunch knows dependencies in current version. So if you want to install
a game which needs powersdl, it will check if it is installed and if not a
requester will pop up and show the dependencies of the application. If the user
continues powersdl gets installed, too. If he cancels the software installation
gets aborted. There is no dependency support for on uninstalling. If the user
decides to uninstall powersdl, it is his choice. Afterwards the games will fail,
but when he simply reinstalls one of them, he gets informed that powersdl is
missing and the system repairs itself. In my opinion this is the best way to go.
One more thing: (yeah stolen)
I only have a few testers right now, as it is required to have some experienced
people to find the flaws and bugs as well as provide ideas of features I forgot.
So far they seem to be happy with the result and the number of applications in
list is that small, because I asked them to now send any in until the database
format is settled. :)
Geit
Cet article provient de Meta-MorphOS
https://www.meta-morphos.org/viewtopic.php?topic=829&forum=52