2011-01-04, 23:26
Hey X3lectric,
don't be offended by the dialog clutter. Really.
It doesn't mean I don't like the script. I only found it not to clear to dig in.
Keep in mind that the reason I don't like it is also partly because of my background.
Alsa came out not correctly installed.
I've done a simple test:
install karmic, install xci w alsa 1.0.23 -> check alsa versions.
reinstall karmic, install xci with std alsa ver.), my alsa script -> check alsa version.
On the alsa site, there is an alsa-info script, that shows the version of it.
I don't rember the details; but 3 items should have been set to 1.0.23.
After XCI installation (with 1.0.23) only 2 items are set the correct version.
That caused me many many crashes and hours of testing, but finally I could fix that by another alsa install.
Finding another working script made me comparing both scripts as the first thing, but that didn't bring me much further: They appear doing about the same thing, the same way!
With all these vague facts I don't think it was worthed to post it here.
Not so many people are willing to dig in the code. So I left it as it was.
I understand your frustration about people only installing and not looking further. But sometimes, the knowledge and courage is not there to do so.
The ever recurring ppa problems are not your problem indeed. And you're not the first one that encounters the problem.
But would it not be interesting to have own ppa's that shield off regression?
After all: installation with xci for the 256 version was not working anymore.
(I'll see tomorrow when I test it, I have time)
Dunno how to do that to be honest, it's only the idea, and maybe that could get the installations make more stable. With external ppa's, XCI stays dependent and gets the impact when one of them is failing.
I'll have a further look at the final script, maybe there is something I can do. And if it turns out with improvements etc (chances are that I cannot do better then you!), I'll contact you for svn access.
I'm interested in having this working too. But it must be maintainable.
Like it is now, I think it's a hard job.
So don't be disappointed or so if no one is taking over the ownership, you've done a great job till now. (moreover giving circumstances!)
And that I find this a hard-to-maintain, could also be seen as something that tells more about me then you
About the menu thing: I was only curious in the hope to find solutions.
(I don't even know how to do it)
So it's not something I like or not, or I want or force it *my* way.
As long it does the job in the end. That's what most people only care of anyway. (unfortunately sometimes)
So again, for tomorrow; I'll rerun some tests and add feedback.
CU around, and thx for the reply!
don't be offended by the dialog clutter. Really.
It doesn't mean I don't like the script. I only found it not to clear to dig in.
Keep in mind that the reason I don't like it is also partly because of my background.
Alsa came out not correctly installed.
I've done a simple test:
install karmic, install xci w alsa 1.0.23 -> check alsa versions.
reinstall karmic, install xci with std alsa ver.), my alsa script -> check alsa version.
On the alsa site, there is an alsa-info script, that shows the version of it.
I don't rember the details; but 3 items should have been set to 1.0.23.
After XCI installation (with 1.0.23) only 2 items are set the correct version.
That caused me many many crashes and hours of testing, but finally I could fix that by another alsa install.
Finding another working script made me comparing both scripts as the first thing, but that didn't bring me much further: They appear doing about the same thing, the same way!
With all these vague facts I don't think it was worthed to post it here.
Not so many people are willing to dig in the code. So I left it as it was.
I understand your frustration about people only installing and not looking further. But sometimes, the knowledge and courage is not there to do so.
The ever recurring ppa problems are not your problem indeed. And you're not the first one that encounters the problem.
But would it not be interesting to have own ppa's that shield off regression?
After all: installation with xci for the 256 version was not working anymore.
(I'll see tomorrow when I test it, I have time)
Dunno how to do that to be honest, it's only the idea, and maybe that could get the installations make more stable. With external ppa's, XCI stays dependent and gets the impact when one of them is failing.
I'll have a further look at the final script, maybe there is something I can do. And if it turns out with improvements etc (chances are that I cannot do better then you!), I'll contact you for svn access.
I'm interested in having this working too. But it must be maintainable.
Like it is now, I think it's a hard job.
So don't be disappointed or so if no one is taking over the ownership, you've done a great job till now. (moreover giving circumstances!)
And that I find this a hard-to-maintain, could also be seen as something that tells more about me then you
About the menu thing: I was only curious in the hope to find solutions.
(I don't even know how to do it
)So it's not something I like or not, or I want or force it *my* way.
As long it does the job in the end. That's what most people only care of anyway. (unfortunately sometimes)
So again, for tomorrow; I'll rerun some tests and add feedback.
CU around, and thx for the reply!
