> On Wed, Nov 27, 2013 at 06:07:12PM +0100, Raphaël wrote:
>On Mon, Aug 05, 2013 at 06:39:35PM +0200, Jostein Berntsen wrote:
>> Any news on release plans for a new version? 
>
>
>Following Roger's advise a live Gentoo ebuild for abook (git) is
>provided here [1] so that gentoo'ist can test it further before tagging
>and releasing.
>
>
>
>[1] https://bugs.gentoo.org/show_bug.cgi?id=462338


I personally don't mind Live EBuilds or EBuild files containing CVS/SVN/GIT 
repositories as long as they're properly masked from common users accidentally 
pulling them into their system.  The reason I enjoy the live ebuilds, I can 
very easily build and test recent code from projects I have not imported using
CVS/SNV/GIT, nor desire spending the time setting up the development 
environment for compiling and installing the application.  Live EBuilds also 
seem to exploit the Gentoo platform for what it was likely initially engineered 
to do to begin with.  (ie. Meet the recent library depends more easily, depends 
required by developers when coding their program or application.)  Instead, 
Gentoo only makes meeting depends more easily, while not encouraging Live 
EBuilds which further exploits this feature.

However I need to mention, many of the Gentoo EBuild repository developers 
frown upon CVS/SVN/GIT builds as they're afraid of admitting unstable code, or 
encouraging packages to release stable snapshots.  (The later already has 
plenty of influence from other more popular binary distros.  And further 
masking the Live EBuild already encourages stable packages.)  I strongly feel 
the some of the Gentoo maintainers or volunteers discouraging live EBuilds, are 
cutting themselves short by omitting one of Gentoo's strong features.

Gentoo Live EBuilds (ie. EBuilds built using CVS/SVN/GIT repositories) promote 
the following:

1) Target a larger audience for testing code.  (Albeit, only some testers 
submit bug reports, but a larger audience should exponentially increase 
possible bug reports, encouraging more stable code. ;-)

2) Easier compiling and installing of CVS/SVN/GIT repositories.

3) Gentoo now has several more FEATURES for debugging nowadays, then in the 
past years. (ie. 'splitdebug' - along side keeping source code after 
installing, along side 'noclean' or 'installsources' for keeping the source 
code after install.)  A lot of these features can be enabled only for certain 
EBuilds by using the now standard "/etc/portage/package.env" & 
"/etc/portage/env/" files/folders!


The one area where they may have some reasonable excuse, having a lower-level 
package for which is heavily depended on by the system being a development 
version, which would cause higher-level packages depending on it problems. (ie. 
 
Causing users to unknowingly submit bugs to bugs.gentoo.org instead of 
upstream.)  However, the majority of Live EBuilds refused are higher-level 
entry-level applications not having any code depend on it and are already 
appropriately masked.

So in short, don't be surprised if they mark the Live EBuild as closed.  What 
happens when you admit Debian-minded folks into a feature rich Distro. ;-)

... or you might get lucky, as the Mutt EMail client is heavily used by smarter 
folks!  (Sorry for the extended EMail, but wanted to clarify this as I guess I 
gave advice on using Live EBuilds somewhere previously!)


-- 
Roger
http://rogerx.freeshell.org/


------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
_______________________________________________
Abook-devel mailing list
Abook-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/abook-devel

Reply via email to