Hello ! I had a doubt regarding the PackageInfo WebApp project. You've mentioned about getting a pointer to the exact sources of a package using SWHID's in this mailing list before. Also, as far as I could tell, this project is supposed to be something that users can easily install on their own systems, or self-host on a vps somewhere, instead of providing a central service where users can go to. 1) Most mainstream distros do have some packages already added to the SWHID archive, but there are a lot of packages that are missing. Since every user of this software will be maintaining and updating their own copy of the database, will they be pulling down sources of every package, calculating the SWHID, and requesting to put it on the archive (if not already present), or should we have a central database where users can query to get the SWHID (if already present) ? 2) Regarding getting the package metadata of all distros, I had made a test script using that spins of docker containers of Ubuntu, Fedora and Arch Linux, uses the respective package managers, and get the package information. But while listing entire package lists, very little information is extracted. To get more detailed stuff like the link to the .deb / .rpm file, download size, md5 hash etc. we have to query it on a per package basis. Would it be viable ( and maybe faster ) to not use the package managers, instead get the DB files ( like http://mirror.rise.ph/archlinux/core/os/x86_64/core.db ) from a mirror and parse them directly ?
---- Λαμβάνετε αυτό το μήνυμα απο την λίστα: Λίστα αλληλογραφίας και συζητήσεων που απευθύνεται σε φοιτητές developers \& mentors έργων του Google Summer of Code - A discussion list for student developers and mentors of Google Summer of Code projects., https://lists.ellak.gr/gsoc-developers/listinfo.html Μπορείτε να απεγγραφείτε από τη λίστα στέλνοντας κενό μήνυμα ηλ. ταχυδρομείου στη διεύθυνση <gsoc-developers+unsubscribe [ at ] ellak [ dot ] gr>.