Desiderata API

@cmacmackin

I start writing some idea about I would like FLATPack looks like. This is just a memo where writing working in progress thoughts:
- client API:
- mantaing a local _plain text database file_ of installed packages:
- plain (flat) text allow many awesome things like sharing between us configuration, easy crestion of awesome lists...;
- data saved into the database: mandatory should be _package name_ and _installation path_ and _dependecies_;
- query the remote _user defined repositories_ for searching packages;
- resolve conflicts like the same package on different repository (prompting the user to make non ambiguos choice);
- install and unistall packages handling dependencies, allowing options for clean not still necessary dependecies;
- _server_ API:
- not a centralized sever (not a server at all), but just a remote git repository exposing a FLATPack database where packages are _classified_ and which can be interrogatdd by client FLATPack:
- such a database list packages, their dependencies (that are copied on client database when a package is installed) and they can installed (compiled from sources, building tool yo be used, binary install...).

For the _database_ language/syntax I suggest **json**: Python has a lot of modules for json and now also Fortran has a great one :-) Json is a good compromise: it is still human readable, but it can handle more complex structures than INI file gor example, moreover json is a well establidhed standard.

I like the idea to have github repositories collecting database of Fortran packages that users can interrogate to easy install them.

These are just starting ideas that tonight come to me...