Actually, there were a lot of discussions about packaging these days  
which covered many aspects of the problem.
    I am then writing this article to discuss and sum up what we should do. 
This isn't a question nor an answer, it's a invitation for everybody to build 
ideas and concretise our wishes.
   On the first hand, I'd like to discuss the packaging process, architecture, 
etc... I am still a novice but may be my suggestions would be welcome.
      - The first issue,  as far as I know, is unified technical standards  to 
build rpms. This issue should be adressed to Novell/SUSE, after analysing the 
technical documetation presented in Novell's website and looking for missing 
information. A build server should be created.
     - If they gave a positive reaction,  then the next issue would be RPM 
trees, I suggest the following branches:
          +  official : RPMs approved by the OpenSUSE community, ( could be 
the current inst-source repository )
          + community : Unofficial RPMs, built by volunteers from all over the 
community, after testing, migration to official must be approved by the 
community, ( respects patents, open source )
          + java : Due to the importance of Java applications, java packages 
should have their own branch.
          + extra : free redistributable packages ( non open source ), may 
contain dummy packages with scripts to download and install commercial 
packages ( ATI, NVIDIA, firmwares) like YOU.
          + nonfree : open source packages with licensing problems ( MP3, dvd 
playback, win 32 codecs ... )
     ( In parallel , there should be another "devel" tree containing the same 
branches )
            At this state, OpenSUSE would be in a better shape. And the 
commnity would be able to concentrate on more exotic projects ( My ideas : 
SUSE Live CD creator ; Yast package installation in command line ( install 
<package> uninstall <package> ) with compatibility with many repositories ) ; 
Klik for SUSE ; Server Edition, Network Firewall Edition, .... )

The real questions are: 
    Who can do manage this ?
    How can Novell help us ?
              .......
Please critisize, comment, suggest.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to