Mailinglist Archive: opensuse-buildservice (375 mails)
| < Previous | Next > |
[opensuse-buildservice] Import instead of _link
- From: Dirk Stoecker <opensuse@xxxxxxxxxxxx>
- Date: Tue, 1 Apr 2008 18:14:32 +0200 (CEST)
- Message-id: <alpine.LNX.1.10.0804011806000.29698@xxxxxxxxxxxxxxxxx>
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.
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).
Advantages:
- No longer lots of copies of support packages in all different
repositories.
- Reduced space requirements
- No longer differing version/revision numbers for equal RPM's
- One way to get rid of the thousands of repositories problem
Disadvantages:
- Client support required (probably in installation phase)
- Possibly multiple repositories required for one installation
Ciao
--
http://www.dstoecker.eu/ (PGP key available)
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
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.
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).
Advantages:
- No longer lots of copies of support packages in all different
repositories.
- Reduced space requirements
- No longer differing version/revision numbers for equal RPM's
- One way to get rid of the thousands of repositories problem
Disadvantages:
- Client support required (probably in installation phase)
- Possibly multiple repositories required for one installation
Ciao
--
http://www.dstoecker.eu/ (PGP key available)
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
| < Previous | Next > |