I understand that some have expressed an interest in the ideas I have
proposed for a package search resource, and single click install with
( For those who don't know what I'm talking about see
So I thought I'd inject some life into this mailing list by bringing
up the question of whether we can get some of the required
infrastructure in place in time for 10.3. While we still have 3 months
or so of development time before feature freeze.
I know Martin Vidner was trying to work out how to get the package
search service code I developed running. I have now created some
scripts to simplify this , and updated the README file to explain all
the steps needed to get this working. The updated version is at
So why would we want to put these things in place?
With the package search and metapackage handing functionality in place
- Users could easily locate software whatever repository it are
located in, and whatever the package is named
- They could install it with a single action without having to
comprehend the concept of adding and removing repositories first.
I think this would make our most frequently asked questions a non-issue.
So enough of why we should do it, what needs to be done?
- Confirm a design for the search service.
- Agree on the schemas.
- Agree where we can host the search services
- Develop to a state where it can actually be made public.
- Utilise the resource within the package management user interface
- UI design work
- Usability testing?
- Confirm design for metapackages
- Agree on format, xml schemas, can we bundle rpm files with schema
to make ISV distribution easy etc.
- libzypp support for using a repository only temporarily.
- libzypp support for .repo files to enable identifying repository duplicates
- Implement user interface for installing these, along with KDE/GNOME
mime type file handlers to open the packages with the handler from
links in web pages or clicking on the package on local filesystem.
- Security issues (can we show warning & summary of changes to user
before they su to root, to mitigate any potential issues from
Hope that is enough to start some discussion.
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-devel+help(a)opensuse.org