On Mon, 9 Jan 2006, Richard Bos wrote:
> > Correct. The metadata / patch description stuff is documented in the
> > yast2-packagemanager-devel package
> > (/usr/share/doc/packages/yast2-packagemanager/*).
[...]
> Please copy and past the relevant text. So we do not all to install
> 25Megs and dig through it to read only 1k....
It's too much stuff to copy and past via mail. I can provide you with a
tar.bz2 copy of those files, if you like (via private mail).
> > > Just dealing with YaST2 sources for now, not YOU yet. For now you
> > > need to add the updates repository in APT format. But I plan to add
> > > YOU support in all of it's glory as soon as possible. :)
> >
> > ... we have a feature request pending to enable repomd on YOU trees.
> > Chances are good that we will get this to work for 10.1.
>
> What about repomd'ing everything that suse provides. Think about
> suse-people, suse-projects directories. But also provide similar
> repodata repositories for kotd, mozilla, wine and last but not least
> security updates!!!
As those different repos are all managed by different people, it's not
that easy to have all of them providing repomd stuff. At least the mozilla
projects dirs have beend "repomded" already...
> > (However there is one issue with this approach: The YOU trees contain
> > scripts, which would only be accessible if SMART /
> > $other_package_manager would implement the methods to access the
> > metadata / patch description stuff of the YOU trees. I'm pretty sure
> > APT isn't / wasn't able to access those parts of the updates either.)
>
> See above this would be awesome to have, but if I was in charge of
> moving things from an apt repository to repodata I would put this
> somewhere on the bottom of my TODO list. Christoph any idea when we can
> have a repomd repository originated at suse similar to the apt
> repository?
>
> A new structure on the server can be created like apt:
> ..../suse/apt
> ..../suse/rmd/10.0-i586/
> rmd = repomd or repo metadat (that is its official name)
> This directory can contain links to e.g.
> packman -> misc/packman/suse-10.0
> suser-rbos -> ~misc/apt4rpm/10.0
> base -> /ftp/pub/opensuse/distribution/SL-10.0-OSS/inst-source/suse
> update -> where are the updates located?
>
> It would be nice to see something happening in this direction...
IMHO this is something that we will need (and have) as soon as the build
services goes public with a lot of different repos.
Regards
Christoph
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
