[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-debian
Subject:    apt protocol handler
From:       Kevin Krammer <kevin.krammer () gmx ! at>
Date:       2004-01-19 22:23:37
Message-ID: 200401192323.42755.kevin.krammer () gmx ! at
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Hi again,

thanks for all your input, special thanks to Marcin Pawlik for the help on 
apt.

This is my current concept for an apt protocol handler:

- Input is an URL: format not yet specified, input welcome

- The handler starts as a normal user (might even work as an restricted user)
- it checks the URL for validity, maybe also availablity of host and package 
description.

- it then creates a directory structure for apt, an special apt.conf using 
this directory structure, a sources.list file using the default sources.list 
file and the resource from the URL.

- runs apt-get update -c created-config-file

- offers the user one preselected package (the one from the URL) and a 
possibility to see other available from the same source.

- can at any time call apt-cache on its local structure to check dependencies.

- After user chose install, ask for root password
- either use previously generated sources.list for the main installer or hand 
over the URL

The idea is, to do as much as possible without root privileges.
Disadvantage is that some operations will be done twice.

Any thoughts?

Cheers,
Kevin

-- 
Kevin Krammer <kevin.krammer@gmx.at>
Qt/KDE Developer, Debian User
www.mrunix.de - Unix/Linux programming forum
www.qtforum.org - Qt programming forum

[Attachment #5 (application/pgp-signature)]

_______________________________________________
kde-debian mailing list
kde-debian@kde.org
https://mail.kde.org/mailman/listinfo/kde-debian


[prev in list] [next in list] [prev in thread] [next in thread]