https://bugzilla.novell.com/show_bug.cgi?id=880146
https://bugzilla.novell.com/show_bug.cgi?id=880146#c27
--- Comment #27 from Stanislav Brabec 2014-06-04 17:06:02 CEST ---
1. It could be a Factory devel project for selected packages.
2. I agree. Subprojects make sense only for reasons listed in the comment 11.
Over-sub-projecting ends with complicated setups and lots of aggregates.
Large projects create no problems, as long as they do not replace generic
libraries by later incompatible versions.
3. Yes. Feel free to move anything you consider as useful and replace obsolete
versions in the current electronics projects.
4. Even two versions can co-exist in a single repository (and sometimes in a
single computer) as long as they don't produce equally named packages. You just
need a properly set Provides, Conflicts in the spec, and Prefer in prjconf.
foo-next.spec
Version: 1.1.1
Provides: foo = %{version}
# Optional, only in case of file conflict
# (update-alternatives could be another solution)
# You can also use Conflicts
# (then user will be asked for removal before replacement)
Obsoletes: foo < %{version}
%package devel
... similar same as above
And project prjconf (if you see ambiguity build error):
Prefer: foo
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.