Mailinglist Archive: opensuse-kde (246 mails)

[Lubos Lunak <l.lunak@xxxxxxx>]

On Thursday 18 of March 2010, todd rme wrote:
> On Thu, Mar 18, 2010 at 5:30 AM, Lubos Lunak <l.lunak@xxxxxxx> wrote:
> > ...
> > There is a reason why adding
> > community repositories in Yast fetches a list of those from a 3rd party
> > site and knows nothing else than the URL of that list. Yes, this all
> > sucks. ...
>
> Could doing this be the solution?  The program would have a trusted
> third-party list of file types and associated package repositories
> that the program would download periodically and check against.

 That is very similar to "MP3 support is missing, press Yes to install it from 
Packman", so as I said, unlikely.

> Alternatively, you could provide a program that detects something is
> missing, and third-party repositories could provide packages that add
> a list of what they could provide.  So when you are missing MP3
> support, the software will query the lists provided by the
> repositories and grab the package that provides that capability.  So,
> for instance, packman could provide a "package-detection-lists" rpm
> that installs a list of media types it can provide, and the KDE
> program consults that list (along with similar lists from other repos)
> when it detects a problem.  If multiple repositories provide the same
> capability, the zypper solver would have to take over.

 I don't see how this could solve the problems I described. Repositories 
already offer a list of packages that they provide, and this list is used 
when the repository is added e.g. in yast. But before it's added, this 
information cannot be read, so it doesn't solve anything. The same way we 
cannot install by default a rpm provided by Packman.

> It might even be possible to set up so that when you add a repository
> it automatically queries the repository for this list and installs it
> if it is available (updating it along with repository updates if it
> has changed).

 I don't understand this either. When the repository is added in yast, the 
problem is already basically solved.

-- 
 Lubos Lunak
 openSUSE Boosters team, KDE developer
 l.lunak@xxxxxxx , l.lunak@xxxxxxx
-- 
To unsubscribe, e-mail: opensuse-kde+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-kde+help@xxxxxxxxxxxx