Le 12.12.2014 14:00, Martin Read a écrit :
Notably, there is neither a billing framework, nor a place to put
one.
True.
But it would not be that hard to adapt it. Let's try a basic algo:
#echo my.paying.repo >> /etc/apt/sources.list
#apt-get update
#mybillingscrip PackageIWantToPayFor
-> ask for you ssh key, or maybe use what ssh-agent already have. If
server wants, it can use a multi-identification system (ssh can require
more than a single identifier, for example it supports challenge
authentication).
-> ask apt-rdepends what you need to install
-> ask the server to prepare needed paying files in a dedicated folder.
-< the server looks various numbers in a database (money client still
have, sum of money the packages cost)
-< if enough money in client's account, remove the sum, copy the files
in a dedicated place
-< server notices the client that it's ready to download
-> download packages with sftp
-> server remove files when they are downloaded
-> install packages as usual, with dpkg or whatever
See? No need for client-side framework, I'm sure a simple script can do
it, and it is probably doable in less than a week by someone not used to
apt and scripting.
The point where it will be harder is server-side, depending on the
software you are using to manage your payments.
Other than that, it's only a matter of identifying the user, as far as
I can understand.
Of course, I'm not used to using apple or microsoft or google OSes with
app stores, so I probably miss one or more check. They could use
something different than ssh, for example. And they probably have a nice
GUI to allow the user to fill his account easily.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/b885ddd449e0df0bf21b710e1a564...@neutralite.org
