Feature added by: Sascha Manns (saigkill)
Feature #305866, revision 1, last change by Title: osc/obs: load Packages from every Project without Link
Buildservice: Unconfirmed Priority Requester: Neutral
Requested by: Sascha Manns (saigkill)
Description: If i build Packages with OBS/OSC, i must link Packages from other Project to my own. I wish me, that future Releases from OBS/OSC solve the depencies automaticly, and load the Packages from every Repository. Other Way, is if we give Repositories an Priority Number. So the OSC/OBS works first with the high Priority Repos.
Feature changed by: Marek Stopka (m4r3k) Feature #305866, revision 2 Title: osc/obs: load Packages from every Project without Link
Buildservice: Unconfirmed Priority Requester: Neutral
Requested by: Sascha Manns (saigkill)
Description: If i build Packages with OBS/OSC, i must link Packages from other Project to my own. I wish me, that future Releases from OBS/OSC solve the depencies automaticly, and load the Packages from every Repository. Other Way, is if we give Repositories an Priority Number. So the OSC/OBS works first with the high Priority Repos.
+ Discussion: + #1: Marek Stopka (m4r3k) (2009-02-18 12:38:54) + I don't think this is a good idea... How you wanna choose right project + to use package from?
Feature changed by: Sascha Manns (saigkill) Feature #305866, revision 3 Title: osc/obs: load Packages from every Project without Link
Buildservice: Unconfirmed Priority Requester: Neutral
Requested by: Sascha Manns (saigkill)
Description: If i build Packages with OBS/OSC, i must link Packages from other Project to my own. I wish me, that future Releases from OBS/OSC solve the depencies automaticly, and load the Packages from every Repository. Other Way, is if we give Repositories an Priority Number. So the OSC/OBS works first with the high Priority Repos.
Discussion: #1: Marek Stopka (m4r3k) (2009-02-18 12:38:54) I don't think this is a good idea... How you wanna choose right project to use package from?
+ #2: Sascha Manns (saigkill) (2009-02-18 12:55:06) + I thought that we can give Prioritys as in Yast-Repositories.
Feature changed by: Marek Stopka (m4r3k) Feature #305866, revision 4 Title: osc/obs: load Packages from every Project without Link
Buildservice: Unconfirmed Priority Requester: Neutral
Requested by: Sascha Manns (saigkill)
Description: If i build Packages with OBS/OSC, i must link Packages from other Project to my own. I wish me, that future Releases from OBS/OSC solve the depencies automaticly, and load the Packages from every Repository. Other Way, is if we give Repositories an Priority Number. So the OSC/OBS works first with the high Priority Repos.
Discussion: #1: Marek Stopka (m4r3k) (2009-02-18 12:38:54) I don't think this is a good idea... How you wanna choose right project to use package from?
#2: Sascha Manns (saigkill) (2009-02-18 12:55:06) I thought that we can give Prioritys as in Yast-Repositories.
+ #3: Marek Stopka (m4r3k) (2009-02-18 13:12:38) (reply to #2) + There are thousands of projects in buildservice, good luck with it :-)
Feature changed by: Sascha Manns (saigkill) Feature #305866, revision 5 Title: osc/obs: load Packages from every Project without Link
Buildservice: Unconfirmed Priority Requester: Neutral
Requested by: Sascha Manns (saigkill)
Description: If i build Packages with OBS/OSC, i must link Packages from other Project to my own. I wish me, that future Releases from OBS/OSC solve the depencies automaticly, and load the Packages from every Repository. Other Way, is if we give Repositories an Priority Number. So the OSC/OBS works first with the high Priority Repos.
Discussion: #1: Marek Stopka (m4r3k) (2009-02-18 12:38:54) I don't think this is a good idea... How you wanna choose right project to use package from?
#2: Sascha Manns (saigkill) (2009-02-18 12:55:06) I thought that we can give Prioritys as in Yast-Repositories.
#3: Marek Stopka (m4r3k) (2009-02-18 13:12:38) (reply to #2) There are thousands of projects in buildservice, good luck with it :-)
+ #4: Sascha Manns (saigkill) (2009-02-18 13:25:33) (reply to #3) + Hmm. Yes you're right. This is to difficult. That was a fixed idea ...
Feature changed by: Andreas Jaeger (a_jaeger) Feature #305866, revision 6 Title: osc/obs: load Packages from every Project without Link
- Buildservice: Unconfirmed + Buildservice: Evaluation Priority Requester: Neutral
Requested by: Sascha Manns (saigkill)
Description: - If i build Packages with OBS/OSC, i must link Packages from other - Project to my own. I wish me, that future Releases from OBS/OSC solve - the depencies automaticly, and load the Packages from every Repository. - Other Way, is if we give Repositories an Priority Number. So the - OSC/OBS works first with the high Priority Repos. + If I build packages with OBS/OSC, I must link packages from other + projects to my own. I wish that future releases from OBS/OSC solve the + depencies automaticly, and load the packages from every repository. + Other Way, is if we give repositories a priority number. So the OSC/OBS + works first with the high priority repositories.
Discussion: #1: Marek Stopka (m4r3k) (2009-02-18 12:38:54) I don't think this is a good idea... How you wanna choose right project to use package from?
#2: Sascha Manns (saigkill) (2009-02-18 12:55:06) I thought that we can give Prioritys as in Yast-Repositories.
#3: Marek Stopka (m4r3k) (2009-02-18 13:12:38) (reply to #2) There are thousands of projects in buildservice, good luck with it :-)
#4: Sascha Manns (saigkill) (2009-02-18 13:25:33) (reply to #3) Hmm. Yes you're right. This is to difficult. That was a fixed idea ...
+ #5: Andreas Jaeger (a_jaeger) (2009-07-09 16:59:28) + Still wouldn't it work to name repositories instead of linking?
Feature changed by: Andreas Jaeger (a_jaeger) Feature #305866, revision 7 Title: osc/obs: load Packages from every Project without Link
Buildservice: Evaluation Priority Requester: Neutral
Requested by: Sascha Manns (saigkill)
Description: If I build packages with OBS/OSC, I must link packages from other projects to my own. I wish that future releases from OBS/OSC solve the depencies automaticly, and load the packages from every repository. Other Way, is if we give repositories a priority number. So the OSC/OBS works first with the high priority repositories.
Discussion: #1: Marek Stopka (m4r3k) (2009-02-18 12:38:54) I don't think this is a good idea... How you wanna choose right project to use package from?
#2: Sascha Manns (saigkill) (2009-02-18 12:55:06) I thought that we can give Prioritys as in Yast-Repositories.
#3: Marek Stopka (m4r3k) (2009-02-18 13:12:38) (reply to #2) There are thousands of projects in buildservice, good luck with it :-)
#4: Sascha Manns (saigkill) (2009-02-18 13:25:33) (reply to #3) Hmm. Yes you're right. This is to difficult. That was a fixed idea ...
#5: Andreas Jaeger (a_jaeger) (2009-07-09 16:59:28) Still wouldn't it work to name repositories instead of linking?
+ #6: Andreas Jaeger (a_jaeger) (2009-07-09 17:02:35) + Can this be considered a duplicate of 305689 - or is that a complete + different use case?
Feature changed by: Adrian Schröter (adrianSuSE) Feature #305866, revision 9 Title: osc/obs: load Packages from every Project without Link
- Buildservice: Evaluation + Buildservice: Rejected by Adrian Schröter (adriansuse) + reject date: 2009-08-10 10:56:18 + reject reason: If I build packages with OBS/OSC, I must link packages + from other projects to my own. I wish that future releases from OBS/OSC + solve the depencies automaticly, and load the packages from every + repository. + Other Way, is if we give repositories a priority number. So the OSC/OBS works + first with the high priority repositories. Priority Requester: Neutral
Requested by: Sascha Manns (saigkill)
Description: If I build packages with OBS/OSC, I must link packages from other projects to my own. I wish that future releases from OBS/OSC solve the depencies automaticly, and load the packages from every repository. Other Way, is if we give repositories a priority number. So the OSC/OBS works first with the high priority repositories.
Discussion: #1: Marek Stopka (m4r3k) (2009-02-18 12:38:54) I don't think this is a good idea... How you wanna choose right project to use package from?
#2: Sascha Manns (saigkill) (2009-02-18 12:55:06) I thought that we can give Prioritys as in Yast-Repositories.
#3: Marek Stopka (m4r3k) (2009-02-18 13:12:38) (reply to #2) There are thousands of projects in buildservice, good luck with it :-)
#4: Sascha Manns (saigkill) (2009-02-18 13:25:33) (reply to #3) Hmm. Yes you're right. This is to difficult. That was a fixed idea ...
#5: Andreas Jaeger (a_jaeger) (2009-07-09 16:59:28) Still wouldn't it work to name repositories instead of linking?
#6: Andreas Jaeger (a_jaeger) (2009-07-09 17:02:35) Can this be considered a duplicate of 305689 - or is that a complete different use case?
Feature changed by: Adrian Schröter (adrianSuSE) Feature #305866, revision 10 Title: osc/obs: load Packages from every Project without Link
Buildservice: Rejected by Adrian Schröter (adriansuse) reject date: 2009-08-10 10:56:18 reject reason: If I build packages with OBS/OSC, I must link packages from other projects to my own. I wish that future releases from OBS/OSC solve the depencies automaticly, and load the packages from every repository. Other Way, is if we give repositories a priority number. So the OSC/OBS works first with the high priority repositories. Priority Requester: Neutral
Requested by: Sascha Manns (saigkill)
Description: If I build packages with OBS/OSC, I must link packages from other projects to my own. I wish that future releases from OBS/OSC solve the depencies automaticly, and load the packages from every repository. Other Way, is if we give repositories a priority number. So the OSC/OBS works first with the high priority repositories.
Discussion: #1: Marek Stopka (m4r3k) (2009-02-18 12:38:54) I don't think this is a good idea... How you wanna choose right project to use package from?
#2: Sascha Manns (saigkill) (2009-02-18 12:55:06) I thought that we can give Prioritys as in Yast-Repositories.
#3: Marek Stopka (m4r3k) (2009-02-18 13:12:38) (reply to #2) There are thousands of projects in buildservice, good luck with it :-)
#4: Sascha Manns (saigkill) (2009-02-18 13:25:33) (reply to #3) Hmm. Yes you're right. This is to difficult. That was a fixed idea ...
#5: Andreas Jaeger (a_jaeger) (2009-07-09 16:59:28) Still wouldn't it work to name repositories instead of linking?
#6: Andreas Jaeger (a_jaeger) (2009-07-09 17:02:35) Can this be considered a duplicate of 305689 - or is that a complete different use case?
+ #7: Adrian Schröter (adriansuse) (2009-08-10 11:23:40) + Sorry, my reject reason gots messed up (dunno why). + Rejecting this because loading "from every Project" would break trust, + create build conflicts in masses and almost never build. Just pick any + would not work at build time and still lead to random results. + I agree that we need to do something to help user to find missing + dependencies. But the best what comes to my mind is to improve the + source generators and optionally build a wizard helping the user to + find existing stuff for certain dependencies.
-
fate_noreply＠suse.de