On Tue, 26 Jun 2007, Petr Cerny wrote:
Marcus Rueckert wrote:
On 2007-06-26 14:04:39 +0200, Petr Cerny wrote:
OK, I see. Is the problem - creating package for the sake of logical assignment into projects - solvable via "aggregate"?
aggregate has the same problems on the mirror side as linked packages.
Is it then possible to create some "foolink" which would have the properties of "ln -s" which could be used for sorting packages into different projects/groups? Or some search engine working with software.opensuse.org/download , capable of using Tags from BS? Otherwise people without BS account willo have hard times finding packages (that is if we want them to install packages without invitation from maintainer).
I also would like to have a type of link, which acts as a softlink in the download hierarchy (including the updates of the related meta files). Thought I do not know how to handle packages which have less repositories in their base project, than in the linking destination project. Another disadvantage of links beside space and bandwidth is confusion. Each of the packages has different revisions. For a user it's confusing to know which of the packages is the one to take. Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org