Hello all!
I would like to put forward an idea that I have, which could simplify
the life for Linux users...
The concept is simple, but the implementation is probably not :-/
Today, when I install openSUSE on my machine, it will detect most of my
hardware just fine. But there are some hardware that could not be
identified properly, for instance my monitors.
What I would like to see, is that during the install, some magic is
built in that can automatically (after the user approves) go out to the
internet to see if there are any drivers for the specific hardware.
There should also be an daemon running on the machine, that detects when
new hardware has been attached and there are no available drivers for
it. It should then suggest that it can look it up on the internet.
If a driver is found, it should be downloaded and installed onto the
system.
The hosting website should also be able to keep track of what sort of
hardware that has not been properly identified so that the next version
of the distro can include them.
For something like a monitor, it could be as simple as letting users add
the needed mode lines etc to the website and it would be downloaded and
put into SaX2's database.
I think it would also be good if that same website would know about free
proprietary (but re-distributable) drivers and let the user select
whether he wants to download them or not. We currently have this in the
"Desktop Effects" utility, but users might want to have the driver for
other purposes than a 3D Desktop.
Does anyone think that this would be a good idea and if so, how should
we proceed?
Thanks,
Magnus
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Guys
Just to let you know that it has been announced that the NZ Govt has
announced that the New Zealand Daylight Savings time is being extended
for the 2007-2008 summer season.
Clocks will go forward an hour a week earlier than usual - on the last
Sunday in September- and back an hour on the first Sunday in April.
Please check out:
http://www.dia.govt.nz/diawebsite.nsf/wpg_URL/Services-Daylight-Saving-Dayl…
or shorter form:
http://tinyurl.com/3alozw
For the official details.
Cheers
Jim
--
Jim Pye
PyeNet Universal
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Daniel and Sascha,
I have upload your changes into svn. However, I am not able to compile them with the nsis. The problem is that I can not get the nsis system plugin, as at the wiki pages says that it is included in the latest nsis release. However, it is not included at the linux release. Do you think you could send me the files I need or an idea how to manage that?
Again, thank you very much!
jordi
----- Mensaje original ----
De: Daniel Gollub <dgollub(a)suse.de>
Para: opensuse-project(a)opensuse.org
CC: ssommer(a)suse.de
Enviado: domingo, 29 de abril, 2007 14:51:28
Asunto: Re: [opensuse-project] Testing instlux for OpenSuSE10.3
On Tuesday 24 April 2007 11:05:16 Jordi Massaguer i Pla wrote:
> I am asking you some testing and feedback about it. You can download the
> latest builds from:
>
> http://instlux.sourceforge.net/testing_builds/
Hi Jordi,
Sascha and me have done some basic testing of your test builds. instlux works
quite well so far. We can also verify that it is working for SATA harddisks.
We discovered only some minor issues:
#1 Find Windows partion
find --set-root /autoexec.bat
This would break on several windows installation on different partions. Even
on windows installation which don't have a "autoexec.bat" file in place. (At
least one box i tested with a vendor customized Windows XP doesn't have one.)
We enhanced your nsis script so it create a "stamp file" to mark the Window
partition which triggered the instlux installation:
find --set-root /instlux-hitme.txt
... should be very unique :)
(Feel free to rename the file in something more unique)
#2 Translations
Updated the German translation ... not quite sure about the quality of the
other translations. Maybe you should make a call for proof reading.
#3 Use system screen resolution and selected language
instlux should now start the installation in the user chosen language. The
installation system gets booted with vga=0xXXX parameter and splash=silent.
The screen resolution from the Windows installation is used to determine the
vga value. For some reason the splash screen is not working .. but i guess
your initrd is customized and not the original one - right?
The nsis system plugin is required to get the system resolution
http://nsis.sourceforge.net/System_plug-in
TODO: Some languages aren't handled yet in the nsis script.
#4 instlux grub - timeout 0
The grub of instlux boots know the installation immediately. No need to bother
the user two times with different boot managers.
#5 Check minimum amount of RAM / Harddisk free space (TODO)
For the network installation builds instlux should check if the minimum amount
of RAM is avaliable. If not instlux should give a warning. Maybe we could do
something similar to check if enough harddisk space is left and give
warnings.
#6 make_instlux.py changes
Don't call makensis with absolute path, my version is very very customized.
Maybe we should provide a nsis package with all the required plugins in the
oSBS.
All changes are attachted as patch from the latest revision of SVN. I hope you
could commit them upstream. Beside the background color change to #7ac142
this should be still distribution independent...
best regards,
Daniel
Index: translations/german/license_german.txt
===================================================================
--- translations/german/license_german.txt (revision 18)
+++ translations/german/license_german.txt (working copy)
@@ -2,7 +2,9 @@
Autor: Jordi Massaguer Pla
Mitwirkende:
-Die Leute, die hier verzeichnet werden, haben zum instlux, entweder durch Code beigetragen, indem sie Rückgespräch sendeten oder indem sie förderten. Wenn du denkst, solltest du hier verzeichnet werden, schreibst ein email zu jordimassaguerpla(a)yahoo.es.
+
+Folgende Personen haben durch Code, Rücksprachen oder Förderungen zu instlux beigetragen.
+Wenn Sie ebenfalls als Beigetragender erwähnt werden möchten, schreiben Sie eine E-Mail an jordimassaguerpla(a)yahoo.es.
LIST_OF_CONTRIBUTORS
Deutsche Übersetzung der
Index: src/instlux_template_en.nsi
===================================================================
--- src/instlux_template_en.nsi (revision 18)
+++ src/instlux_template_en.nsi (working copy)
@@ -59,8 +59,9 @@
!include FileFunc.nsh ; GetRoot / un.GetRoot
!insertmacro GetRoot
!insertmacro un.GetRoot
- BGGradient f8e409
+ BGGradient 7ac142
+
!define MUI_ICON "instlux.ico"
!define MUI_UNICON "instlux.ico"
!define MUI_HEADERIMAGE
@@ -100,6 +101,9 @@
var c
var ConfigSYS
var MenuLSTFile
+var HitMeFile
+var Resolution
+var LangParam
Function .onInit
# the plugins dir is automatically deleted when the installer exits
@@ -116,6 +120,7 @@
Pop $0 ; $0 has '1' if the user closed the splash screen early,
; '0' if everything closed normally, and '-1' if some error occurred.
!insertmacro MUI_LANGDLL_DISPLAY
+
FunctionEnd
@@ -171,10 +176,79 @@
lbl_Common:
+ FileOpen $HitMeFile $c\instlux_hitme.txt a
+ FileWrite $HitMeFile "This file was created by instlux."
+ FileSeek $HitMeFile 0 END
+ FileClose $HitMeFile
+
+# TODO add all avaliable languages
+ StrCmp $LANGUAGE ${LANG_ENGLISH} 0 +2
+ StrCpy $LangParam "en"
+ StrCmp $LANGUAGE ${LANG_DUTCH} 0 +2
+ StrCpy $LangParam "da"
+ StrCmp $LANGUAGE ${LANG_FRENCH} 0 +2
+ StrCpy $LangParam "fr"
+ StrCmp $LANGUAGE ${LANG_GERMAN} 0 +2
+ StrCpy $LangParam "de"
+# StrCmp $LANGUAGE ${LANG_KOREAN} 0 +2
+# StrCpy $LangParam "cr"
+# StrCmp $LANGUAGE ${LANG_RUSSIAN} 0 +2
+# StrCpy $LangParam "ru"
+ StrCmp $LANGUAGE ${LANG_SPANISH} 0 +2
+ StrCpy $LangParam "es"
+ StrCmp $LANGUAGE ${LANG_SWEDISH} 0 +2
+ StrCpy $LangParam "se"
+# StrCmp $LANGUAGE ${LANG_TRADCHINESE} 0 +2
+# StrCpy $LangParam "zh_TW"
+# StrCmp $LANGUAGE ${LANG_SIMPCHINESE} 0 +2
+# StrCpy $LangParam "zh_CN"
+# StrCmp $LANGUAGE ${LANG_SLOVAK} 0 +2
+# StrCpy $LangParam "sk"
+
+
+
+ # http://nsis.sourceforge.net/System_plug-in <--- requires
+ System::Call 'user32::GetSystemMetrics(i 0) i .r0'
+ System::Call 'user32::GetSystemMetrics(i 1) i .r1'
+
+
+
+ # 64k | 0x311 0x314 0x317 0x31A
+ IntCmp $0 640 is640 isUnknow 0
+ IntCmp $0 800 is800
+ IntCmp $0 1024 is1024
+ IntCmp $0 1280 is1280 0 is1280
+
+ isUnknow:
+ StrCpy $Resolution "normal"
+ Goto writeMenu
+
+ is640:
+ StrCpy $Resolution "0x311"
+ Goto writeMenu
+
+ is800:
+ StrCpy $Resolution "0x314"
+ Goto writeMenu
+
+ is1024:
+ StrCpy $Resolution "0x317"
+ Goto writeMenu
+
+ is1280:
+ StrCpy $Resolution "0x31A"
+ Goto writeMenu
+
+
+ writeMenu:
+
+
FileOpen $MenuLSTFile $c\menu.lst a
+ FileWrite $MenuLSTFile "hiddenmenu $\r$\n"
+ FileWrite $MenuLSTFile "timeout 0 $\r$\n"
FileWrite $MenuLSTFile "title MENU_TITLE $\r$\n"
- FileWrite $MenuLSTFile "find --set-root /autoexec.bat$\r$\n"
- FileWrite $MenuLSTFile "kernel /distros/KERNEL KRNL_APPEND$\r$\n"
+ FileWrite $MenuLSTFile "find --set-root /instlux_hitme.txt$\r$\n"
+ FileWrite $MenuLSTFile "kernel /distros/KERNEL KRNL_APPEND lang=$LangParam vga=$Resolution splash=silent$\r$\n"
FileWrite $MenuLSTFile "initrd /distros/DRIVERS$\r$\n"
FileSeek $MenuLSTFile 0 END
FileClose $MenuLSTFile
@@ -221,6 +295,7 @@
lbl_Finish:
RMDir /REBOOTOK /r "$c\distros\OUTPATH"
Delete /REBOOTOK "$c\menu.lst"
+ Delete /REBOOTOK "$c\instlux_hitme.txt"
Delete /REBOOTOK "$SMSTARTUP\instlux-uninst.exe"
SectionEnd
Index: make_instlux.py
===================================================================
--- make_instlux.py (revision 18)
+++ make_instlux.py (working copy)
@@ -27,7 +27,7 @@
build = "build"
#nsis_bin = '"c:\Program Files\NSIS\makensis.exe"'
-nsis_bin = '"/usr/bin/makensis"'
+nsis_bin = '"makensis"'
instlux_ico = "instlux.ico"
instlux_logo = "instlux_logo.bmp"
grub4dos = ["grldr","grub.exe"]
______________________________________________
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
danke schön!!
jordi
----- Mensaje original ----
De: Daniel Gollub <dgollub(a)suse.de>
Para: opensuse-project(a)opensuse.org
CC: ssommer(a)suse.de
Enviado: domingo, 29 de abril, 2007 14:51:28
Asunto: Re: [opensuse-project] Testing instlux for OpenSuSE10.3
On Tuesday 24 April 2007 11:05:16 Jordi Massaguer i Pla wrote:
> I am asking you some testing and feedback about it. You can download the
> latest builds from:
>
> http://instlux.sourceforge.net/testing_builds/
Hi Jordi,
Sascha and me have done some basic testing of your test builds. instlux works
quite well so far. We can also verify that it is working for SATA harddisks.
We discovered only some minor issues:
#1 Find Windows partion
find --set-root /autoexec.bat
This would break on several windows installation on different partions. Even
on windows installation which don't have a "autoexec.bat" file in place. (At
least one box i tested with a vendor customized Windows XP doesn't have one.)
We enhanced your nsis script so it create a "stamp file" to mark the Window
partition which triggered the instlux installation:
find --set-root /instlux-hitme.txt
... should be very unique :)
(Feel free to rename the file in something more unique)
#2 Translations
Updated the German translation ... not quite sure about the quality of the
other translations. Maybe you should make a call for proof reading.
#3 Use system screen resolution and selected language
instlux should now start the installation in the user chosen language. The
installation system gets booted with vga=0xXXX parameter and splash=silent.
The screen resolution from the Windows installation is used to determine the
vga value. For some reason the splash screen is not working .. but i guess
your initrd is customized and not the original one - right?
The nsis system plugin is required to get the system resolution
http://nsis.sourceforge.net/System_plug-in
TODO: Some languages aren't handled yet in the nsis script.
#4 instlux grub - timeout 0
The grub of instlux boots know the installation immediately. No need to bother
the user two times with different boot managers.
#5 Check minimum amount of RAM / Harddisk free space (TODO)
For the network installation builds instlux should check if the minimum amount
of RAM is avaliable. If not instlux should give a warning. Maybe we could do
something similar to check if enough harddisk space is left and give
warnings.
#6 make_instlux.py changes
Don't call makensis with absolute path, my version is very very customized.
Maybe we should provide a nsis package with all the required plugins in the
oSBS.
All changes are attachted as patch from the latest revision of SVN. I hope you
could commit them upstream. Beside the background color change to #7ac142
this should be still distribution independent...
best regards,
Daniel
Index: translations/german/license_german.txt
===================================================================
--- translations/german/license_german.txt (revision 18)
+++ translations/german/license_german.txt (working copy)
@@ -2,7 +2,9 @@
Autor: Jordi Massaguer Pla
Mitwirkende:
-Die Leute, die hier verzeichnet werden, haben zum instlux, entweder durch Code beigetragen, indem sie Rückgespräch sendeten oder indem sie förderten. Wenn du denkst, solltest du hier verzeichnet werden, schreibst ein email zu jordimassaguerpla(a)yahoo.es.
+
+Folgende Personen haben durch Code, Rücksprachen oder Förderungen zu instlux beigetragen.
+Wenn Sie ebenfalls als Beigetragender erwähnt werden möchten, schreiben Sie eine E-Mail an jordimassaguerpla(a)yahoo.es.
LIST_OF_CONTRIBUTORS
Deutsche Übersetzung der
Index: src/instlux_template_en.nsi
===================================================================
--- src/instlux_template_en.nsi (revision 18)
+++ src/instlux_template_en.nsi (working copy)
@@ -59,8 +59,9 @@
!include FileFunc.nsh ; GetRoot / un.GetRoot
!insertmacro GetRoot
!insertmacro un.GetRoot
- BGGradient f8e409
+ BGGradient 7ac142
+
!define MUI_ICON "instlux.ico"
!define MUI_UNICON "instlux.ico"
!define MUI_HEADERIMAGE
@@ -100,6 +101,9 @@
var c
var ConfigSYS
var MenuLSTFile
+var HitMeFile
+var Resolution
+var LangParam
Function .onInit
# the plugins dir is automatically deleted when the installer exits
@@ -116,6 +120,7 @@
Pop $0 ; $0 has '1' if the user closed the splash screen early,
; '0' if everything closed normally, and '-1' if some error occurred.
!insertmacro MUI_LANGDLL_DISPLAY
+
FunctionEnd
@@ -171,10 +176,79 @@
lbl_Common:
+ FileOpen $HitMeFile $c\instlux_hitme.txt a
+ FileWrite $HitMeFile "This file was created by instlux."
+ FileSeek $HitMeFile 0 END
+ FileClose $HitMeFile
+
+# TODO add all avaliable languages
+ StrCmp $LANGUAGE ${LANG_ENGLISH} 0 +2
+ StrCpy $LangParam "en"
+ StrCmp $LANGUAGE ${LANG_DUTCH} 0 +2
+ StrCpy $LangParam "da"
+ StrCmp $LANGUAGE ${LANG_FRENCH} 0 +2
+ StrCpy $LangParam "fr"
+ StrCmp $LANGUAGE ${LANG_GERMAN} 0 +2
+ StrCpy $LangParam "de"
+# StrCmp $LANGUAGE ${LANG_KOREAN} 0 +2
+# StrCpy $LangParam "cr"
+# StrCmp $LANGUAGE ${LANG_RUSSIAN} 0 +2
+# StrCpy $LangParam "ru"
+ StrCmp $LANGUAGE ${LANG_SPANISH} 0 +2
+ StrCpy $LangParam "es"
+ StrCmp $LANGUAGE ${LANG_SWEDISH} 0 +2
+ StrCpy $LangParam "se"
+# StrCmp $LANGUAGE ${LANG_TRADCHINESE} 0 +2
+# StrCpy $LangParam "zh_TW"
+# StrCmp $LANGUAGE ${LANG_SIMPCHINESE} 0 +2
+# StrCpy $LangParam "zh_CN"
+# StrCmp $LANGUAGE ${LANG_SLOVAK} 0 +2
+# StrCpy $LangParam "sk"
+
+
+
+ # http://nsis.sourceforge.net/System_plug-in <--- requires
+ System::Call 'user32::GetSystemMetrics(i 0) i .r0'
+ System::Call 'user32::GetSystemMetrics(i 1) i .r1'
+
+
+
+ # 64k | 0x311 0x314 0x317 0x31A
+ IntCmp $0 640 is640 isUnknow 0
+ IntCmp $0 800 is800
+ IntCmp $0 1024 is1024
+ IntCmp $0 1280 is1280 0 is1280
+
+ isUnknow:
+ StrCpy $Resolution "normal"
+ Goto writeMenu
+
+ is640:
+ StrCpy $Resolution "0x311"
+ Goto writeMenu
+
+ is800:
+ StrCpy $Resolution "0x314"
+ Goto writeMenu
+
+ is1024:
+ StrCpy $Resolution "0x317"
+ Goto writeMenu
+
+ is1280:
+ StrCpy $Resolution "0x31A"
+ Goto writeMenu
+
+
+ writeMenu:
+
+
FileOpen $MenuLSTFile $c\menu.lst a
+ FileWrite $MenuLSTFile "hiddenmenu $\r$\n"
+ FileWrite $MenuLSTFile "timeout 0 $\r$\n"
FileWrite $MenuLSTFile "title MENU_TITLE $\r$\n"
- FileWrite $MenuLSTFile "find --set-root /autoexec.bat$\r$\n"
- FileWrite $MenuLSTFile "kernel /distros/KERNEL KRNL_APPEND$\r$\n"
+ FileWrite $MenuLSTFile "find --set-root /instlux_hitme.txt$\r$\n"
+ FileWrite $MenuLSTFile "kernel /distros/KERNEL KRNL_APPEND lang=$LangParam vga=$Resolution splash=silent$\r$\n"
FileWrite $MenuLSTFile "initrd /distros/DRIVERS$\r$\n"
FileSeek $MenuLSTFile 0 END
FileClose $MenuLSTFile
@@ -221,6 +295,7 @@
lbl_Finish:
RMDir /REBOOTOK /r "$c\distros\OUTPATH"
Delete /REBOOTOK "$c\menu.lst"
+ Delete /REBOOTOK "$c\instlux_hitme.txt"
Delete /REBOOTOK "$SMSTARTUP\instlux-uninst.exe"
SectionEnd
Index: make_instlux.py
===================================================================
--- make_instlux.py (revision 18)
+++ make_instlux.py (working copy)
@@ -27,7 +27,7 @@
build = "build"
#nsis_bin = '"c:\Program Files\NSIS\makensis.exe"'
-nsis_bin = '"/usr/bin/makensis"'
+nsis_bin = '"makensis"'
instlux_ico = "instlux.ico"
instlux_logo = "instlux_logo.bmp"
grub4dos = ["grldr","grub.exe"]
______________________________________________
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
So this was discussed during the Status Meeting and now it's here for
a broader discussion. :)
It was suggested that a feature/goal tracking tool (FATE) be adopted
by openSUSE and made public (bug .223290). There are a few reasons for
this:
* This is one of the cases of the wiki being misused for such a thing,
when it's not ideal. Several projects currently use the wiki for goal
tracking. While it's absolutely awesome thath this stuff is public so
that many of us can take a look through, it may not be ideal. Some
examples: Zypp, YaST, KIWI
<http://en.opensuse.org/Build_Service/KIWI/Todo>, UX, Build Service
etc.
* Things are more open to the community; openSUSE does use FATE
currently, but it's Novell's one only open to employees.
Current cons are that it would really take quite some time/effort to put up.
So, the question is: would people in other projects find it useful
(instead of having to use the wiki) to have this, and do you think it
is a good idea?
Regards,
--
Francis Giannaros
Web: http://francis.giannaros.org
IRC: apokryphos on irc.freenode.net
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Dear all,
As agreed during the FOSDEM07, work has been done in order to make
instlux be part of the OpenSuSE10.3. Also, this work has been reported
on the opensuse-project list.
Now, instlux suports OpenSuSE10.3 Alpha 3, both installation medias
(CDROM and internet) and both architectures (i386 and x86_64).
I am asking you some testing and feedback about it. You can download the
latest builds from:
http://instlux.sourceforge.net/testing_builds/
Your help will be appreciated.
thanks,
jordi massaguer i pla
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Greetings all,
I thought I'd send an email out summarising some of the things I have
been working on recently, to obtain some feedback, and maybe even some
help.
= Package Search =
- This is back up for the time being, although I am not confident of
it staying up for long, if it's down or slow when you read this email
I apologise. adrianS has kindly offered to help with hosting when they
have some more resources.
- Set up a design page at http://en.opensuse.org/PKGSearch-design
- Having spent some time reviewing how people were trying to use the
search, I found a large proportion were searching for phrases, not
just package names/contents. Therefore I made the package summaries
searchable too. eg you could find konversation now with:
http://benjiweber.co.uk:8080/webpin/index.jsp?searchTerm=kde+irc+client
or
http://benjiweber.co.uk:8080/webpin/index.jsp?searchTerm=bin%2Fkonversation
or
http://benjiweber.co.uk:8080/webpin/index.jsp?searchTerm=konversation
- There was a performance problem with people searching for very
common and short terms such as "qt" or "kde", this should be fixed
now.
- I've made some slight modifications to the design based on some suggestions.
- I've been working on improving the performance of the trawler, I can
now from a clean database locate, download, parse, index the metadata
for the main official/community & build service repositories in under
half an hour on my desktop. (That's ~900 repositories, ~110,000
packages including summaries/descriptions, ~16,000,000 files),
incremental updates where only some repositories have changed are much
faster.
- Integration with the simple software installation (explained below)
that I've been proposing, with "Install now" links on
http://benjiweber.co.uk:8080/webpin/index-test.jsp
= Simple Software Installation =
The vast majority of the questions we face when there are not serious
things wrong with the distribution are related to issues such as
installation of third party software, multimedia codecs etc.
Explaining to new users the concept of package repositories, how to
add these, and subsequently install software is not trivial.
Furthermore, users should not be forced to grasp these concepts in
order to easily install software, in my opinion.
To solve this we could have a simple file handler that can handle
links in web pages or files on distributable media which automates the
process of adding repositories and installing software.
- I've set up a wiki page outlining the concept at
http://en.opensuse.org/MetaPackage-design
- I've created a functional prototype yast module, Pascal has kindly
made a package which you can try at:
http://bw.uwcs.co.uk/mp/yast2-mpp-0.0-0.suse102.noarch.rpm
After installing this you can try out some demo uses at
http://bw.uwcs.co.uk/test.html
The "install now" links on http://benjiweber.co.uk:8080/webpin/index-test.jsp
Currently the above will only work with konqueror, unless you create
the associations manually for firefox/opera in the same way as they
are configured in konqueror (this is possible, but difficult to
package without having the configuration in the upstream distribution
package)
Martin Schandler is creating a demo page to show how this could be
used to simplify codec installation, for now hopefully you can use
your imagination.
- In the above package there is also a demo yast client to the search
service, you can run with "/sbin/YaST2 PackageSearch" as a normal
user, and search for and install packages from the build service in
the same way as the "Install now" links on the webpin page.
= What I would like help with =
- Please could people try out the demo prototype metapackage handler
described above, and comment on the concept.
- I know ycp only a little, and perl not at all, so if someone could
fix the above into a releasable quality that would be awesome. (source
is also at http://bw.uwcs.co.uk/mp)
= Future =
- Search service joint hosting Novell/Community, adrianS is looking into this.
- Migration of the frontend to the search to opensuse-community.org
- Fix ycp/perl to a releasable state. (someone who knows what they're doing)
- Improve the "Install now" functionality of the search service, by
calculating the repositories each package depends on (it isn't always
just the one the package is located in).
I am currently investigating either a simple method looking at the
repository dependencies in the build service and manual setup for
repositories outside the build service, and a far more complicated
method using the rpm requires & depends.
- Integration with new build service features such as statistics,
using the search service statistics to improve results.
- Using search service to enrich client side software.
That's all I can think of for now.
_
Benjamin Weber
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
We've briefly discussed during the last IRC meeting about what went
bad in 10.2 and how we can do this better for future products,
especially 10.3. I'm mainly interested in process feedback - and not
on feedback that package x is broken (unless that shows a process
problem).
So, let's discuss what we can do better for our next distro,
Andreas
--
Andreas Jaeger, aj(a)suse.de, http://www.suse.de/~aj/
SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Scott asked on http://en.opensuse.org/Meetings/Current the following:
> It seems apparent from the number bugs without a resolution still exist
> in versions 10,0-10,2. A very small number of bugs are closed as Fixed
> in 10,3. Looking at the sheer number of open bugs in 10,0-10,2 it would
> appear that release of a new version only increases functionality at the
> expense of closing and fixing bugs. Can you tell me/us under what
Yes, and this is a problem. The challenge is that some of the bugs are
bugs in the upstream packages and we cannot fix all of these ourselves.
I agree that we're not doing a good enough job in reacting to bugs and
this is on my agenda to change.
> situation/timetable you use to determine the tooling-up for a new
> version and what constitutes a RC - given the number of current
> bugs. Forgive me I am not offering criticism at all, however Novel's Q.A
> compliance would appear at odds with current release pattern of aprox 6
> months. Due to my GMT +10 time difference I will be unable to attend the
> session and trust that a .PDF may be available afterwards. Many Thanks
> for your time.
For the final release candidate, the goal is to ship without any
blockers and we reached that the last releases.
For the alphas, we do basic testing that it installs - but not more.
Andreas
--
Andreas Jaeger, aj(a)suse.de, http://www.suse.de/~aj/
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Hi,
Within the framework of the new web design of *.opensuse.org, we are also discussing the mission statement for the
openSUSE project and we would love to receive your input.
A mission statement - a clear and succinct representation of openSUSE project, a so called "one-liner"
e.g. * openSUSE - Built to fit!
* openSUSE - Have a lot of fun!
* openSUSE - Caffeine for your machine!
* The openSUSE project - A real alternative!
* openSUSE - It's a wild thing!
* openSUSE - An unlimited alternative!
* openSUSE - The adaptable and innovative solution!
It should be included/supported by a set of our values such as open, leading edge distribution, fits everywhere, best
of open source, innovative, user-friendly, comprehensive, etc.
We will select the best three mission statements for further discussion and finally reward the best input with a 50cm
stuffed Tux.
We are looking forward to your ideas.
Thanks in advance,
Sabine Soellheim
Product Marketing Manager
Novell SUSE Linux Products GmbH
Maxfeldstr. 5
90409 Nürnberg
-------------------------------
SUSE Linux Products GmbH: GF: Markus Rex, HRB 16746 (AG Nuernberg)
-------------------------------
Novell, Inc.
SUSE Linux Enterprise 10
Your Linux is Ready http://www.novell.com/linux
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
