-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/12/2014 09:51 AM, Stefan Seyfried wrote:
Am 11.08.2014 um 14:57 schrieb Robert Schweikert:
But the premise "you can just maintain your own non-systemd distribution on OBS" is IMO a plain lie,
Well, other than the necessary build power I am not aware of any limitation in this area. Please fell free to educate me.
Well, I'll not try that, but everybody else probably would have a lot of fun if I did start the effort with
for i in `osc ls openSUSE:Factory`; do case $i in systemd*) continue;; *) ;; esac osc linkpac openSUSE:Factory $i home:seife:factory-nosystemd done
Based on the experience I have with OBS there is nothing in the way for me to set up a subproject in my HOME and build all of openSUSE, create iso images from it etc. I can maintain patches that add sysV init support in the project and do whatever. There may of course be issues that I am not aware of as I have never attempted anything at that scale. Again, please share your knowledge.
If the weather is bad on the weekend, I might actually try. But I fear that I'll pull the wrath of all other OBS users on me and I'd not consider this a fair and good use of the shared resources.
Proclaiming that statements are "lies" is not very constructive.
Yes, "lie" was the wrong word. But I still consider this impractical, since right now 603 packages depend on systemd, and almost all depend on systemd-rpm-macros, so it is nothing that you can "just fix" by replacing the "faulty" component.
But how many of those 603 depend on systemd conditionally? I have some that depend on systemd but also support sysV init. Yes, the sysV init is for older distros but I am certain someone with better RPM macro magic knowledge than me could come up with some clever condition I could test to install sysV init scripts vs. .system files even on a distribution that is nominally systemd. I personally really do not mind the extra maintenance of sysV init scripts, as I am doing it anyway for older distros. In the end as I have pointed out, from my point of view this is up to each package maintainer whether they are willing to have the additional complexity in their spec files, maintain the sysV init scripts, and possibly carry extra patches to the upstream code.
Probably, instead of wasting the build service resources on this experiment, I'd rather try an installation of yocto built x86_64 on my spare openSUSE partition on my notebook. This will only take a few hours to build and on my private resources.
Anyway, this thread has gone long past its usefulness,
I agree, unfortunately many of the comments just regurgitate things that have been said many times and are not very constructive. However, I think there are few things here and there with valuable input. It would be interesting to understand the numbers better. Later, Robert - -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead Public Cloud Architect rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJT6iCuAAoJEE4FgL32d2Uka00H/0osPo5qeeMAYGBvl/W04FbJ HU/i0SqtV8BAMeayegDI4cfk6F2PyEirtGi+SzmXfBs4VAEULlo4ZJYed/bcZr0K KG9R9eo+YNJPSdRAxxWtYT6OIT8q0sazoxo/N8mRc5GzPGKB8MkU1DE9ot0VXb3C pyuDurDEiFfH9d8uUaLlSmEGl0592OUed7WS5fMp7PUp+Upieiji89CX2S36q8rg P+P32OR3wqNCF8Upk6X2pTeYJwyCTxUbixgZh6SJiyo/f/E7zhxLuf7cq2OSCX8E fGelfvkLwFYtoi+GfmJXVZL2z2YTx9/bPZUVkbhMBdx9TQhgR692DUDzYud9hxo= =MB+C -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org