Mailinglist Archive: opensuse-buildservice (375 mails)
| < Previous | Next > |
Re: [opensuse-buildservice] Import instead of _link
- From: Adrian Schröter <adrian@xxxxxxx>
- Date: Wed, 2 Apr 2008 09:59:16 +0200
- Message-id: <200804020959.16943.adrian@xxxxxxx>
On Tuesday 01 April 2008 18:14:32 wrote Dirk Stoecker:
Isn't this done via defining the list of repositories in a project target ?
The one click installation does already support it, when you add multiple
pathes, all of them will be added.
bye
adrian
--
Adrian Schroeter
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
email: adrian@xxxxxxx
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
Hello,
one of the problems of BuildService for me is the fact, that different
projects need different packages and a user now has the possibility to
select a package in project x, project y, project z, ....
Could instead of this a new mechanism be implemented? The project owners
specify "import xxx from yyy" and this tells the users application, that
project yyy is required in case package xxx should be installed.
Isn't this done via defining the list of repositories in a project target ?
This would need client support to work properly, but as Factory is not
released yet, it still can get implemented (old distributions will
complain xxx is missing and a user would need to add yyy by hand before
proceeding).
The one click installation does already support it, when you add multiple
pathes, all of them will be added.
bye
adrian
--
Adrian Schroeter
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
email: adrian@xxxxxxx
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
| < Previous | Next > |