On 18:59 Tue 02 Sep     , Toma wrote:
> In a way, I agree. E is becoming more and more functional and stable.
> But, thats chould be another reason why distros could package it. If
> an application is stable and full of features, why not package it up?
> People have a stigma about non 1.0 packages. If something isnt 1.0
> they straight away call it 'buggy' and not-finished. A classic case of
> this is wine. Wine 0.9.20+all the ones up to 50+ series were stable
> and useful. Then 1.0 came out and a lot of people said 'Whats the
> difference?'. Dont get me started on the KDE 4.0 debarkle. They
> chucked an unfinished DE out the door and said 'We want more
> developers.' while making the users jump into some horrible
> development version.
> 
> So you see my point? Projects tend to release half-cooked stuff and
> expect people to just gobble it up. I think E should never do that. If
> someone has an issue with using non-1.0 packages, then its their loss!
> :)
> 
> On that note, I think the snapshot cycle should be set, with some bug
> hunting done in the week before a snapshot happens. That way we have a
> set development release that people can infact use and we can have a
> good idea of where they are.
> 
> Toma
> 
+1

but only one exception/addition. we're having 'svn' now. let's just
stick to the svn revisions. example:

snapshots date: Sep  1 2008
svn revision: 35759

this information could be posted in a simple README file. 

***

now let's discuss the packaging. it's not the first time when i offer
to use the OpenSUSE Build Service to provide the packages for a major
distributions. the advantages here are clear:

single transparent shema to build packages for all

disadvantages:

distros are differ and has different approach/requirements for the
packages. some requirements are easy to met. the others quite
complicated. example:

each package included into the OpenSUSE official distribution has the
Novell engineer/maintainer responsible for the maintenance of this
package (24/7 support from Novell is a must) during the whole life of 
the selected distribution.

that's why only E16 (without any additions like themes, e16keyedit, 
etc) is provided in OpenSUSE. the guy from Novell (Gnome project) keeps
the maintenance.

here comes another suggestion: let's revise E-wiki/E-site and update the
actual information about the current distribution channels of E. the
information is heavily outdated or absent. 

may be we should set the wiki page for it and make a single link to this
wiki page as a "Download Center"? i'd be glad to set the info about
OpenSUSE.

regards,
sda


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
enlightenment-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Reply via email to