Re: [gentoo-dev] Unused ebuild built_with_use cleanup

2009-10-09 Thread Petteri Räty
Patrick Lauer wrote:
 
 And that's with all the forced migrations for features like use-deps or the 
 removal of built_with_use. So unless there's some strongly needed features 
 there's no need for it. I can't remember any feature in the EAPI 3 list that 
 really looked useful to me, so not adding it now now now doesn't bother me at 
 all. Just causes more confusion for no real benefit. So who cares if it is 
 delayed by a few timeunits, there's much more important stuff to do.
 

Here's two features that by themselves are important enough to get EAPI
3 implemented. Using pkg_pretend it should be possible to eliminate
expected dies from build time and as such improving user experience. An
example is two use flags that conflict with each other. Use dependency
defaults make the life of ebuild writers easier as you don't need to be
careful with version restrictions any more if you have a case where
something has been on by default and then becomes a use flag for
example. This should eliminate cases like causing glibc downgrade in the
depgraph by being careless.

Regards,
Petteri



signature.asc
Description: OpenPGP digital signature


Re: [gentoo-dev] Unused ebuild built_with_use cleanup

2009-10-09 Thread Petteri Räty
Tomáš Chvátal wrote:
 On čtvrtek 08 Říjen 2009,  23:34:10  Petteri Räty wrote:
 Even this is wrong because:
 Hi
 ...
 betelge...@pena ~ $ portageq metadata / ebuild sys-libs/glibc-2.2.5-r10
 IUSE nls

 For most packages old versions are not kept around so just doing
 =cat/foo-X.Y[use] is fine and EAPI 3 is not needed. I haven't come
 across a case that couldn't be done with EAPI 2 yet. Granted the atoms
 can be a bit cleaner with EAPI 3 but considering how much zmedico slacks
 in implementing it, it's best to do migrating now with EAPI 2 than EAPI
 3 in the far future.
 This is not exactly nice of you. And taking in account that you are actualy 
 the council member it makes me feel not entirely happy.
 If we just simply take look onto this:
 http://cia.vc/stats/author/zmedico/
 we can count that Zac commit something into portage every 3 hours. It does 
 not 
 look entirely like slacking...
 So you are basicaly proposing that maintaining the current codebase and 
 improving what we already have is less important than providing new features, 
 that is also not good.
 

I am not suggesting that the work Zac does is worthless. I am saying
that implementing EAPI 3 is not a colossal amount of work and if it was
a priority to him it would have already been implemented. If he feels
offended by my original comment, I have no problem apologizing to him.
Not having EAPI 3 implemented in general is not his fault as many of us
have the needed skills to start helping on the Portage code base. The
reality just is that he is the most likely person to implement it and as
such a very important factor on when it happens.

Regards,
Petteri



signature.asc
Description: OpenPGP digital signature


[gentoo-dev] openrc-0.5.1 arrived in the tree

2009-10-09 Thread Matthias Schwarzott
Hi there!

As some of you have waited long for this to happen, sys-apps/openrc-0.5.1 is 
there. It has a default enabled (eapi-1) useflag oldnet to install the 
old-style network scripts called net.*.
Regardless of this use-flag, the new init-script /etc/init.d/network is always 
installed.

For transition to new-style network script there is something todo I think.
Unordered list of todos:
* hotplug? at least udev does explicitly call in net.* scripts
* New systems should get old or new scripts?
* does new scripts already can do all that was possible with net.* ?

So far I hope the update does not break any system.
In case this happens nevertheless open a bug as usual.

Regards
Matthias



Re: [gentoo-dev] openrc-0.5.1 arrived in the tree

2009-10-09 Thread Alexey Shvetsov
On Пятница 09 октября 2009 21:57:07 Matthias Schwarzott wrote:
 Hi there!
 
 As some of you have waited long for this to happen, sys-apps/openrc-0.5.1
  is there. It has a default enabled (eapi-1) useflag oldnet to install the
  old-style network scripts called net.*.
 Regardless of this use-flag, the new init-script /etc/init.d/network is
  always installed.
 
 For transition to new-style network script there is something todo I think.
 Unordered list of todos:
 * hotplug? at least udev does explicitly call in net.* scripts
 * New systems should get old or new scripts?
 * does new scripts already can do all that was possible with net.* ?
 
 So far I hope the update does not break any system.
 In case this happens nevertheless open a bug as usual.
 
 Regards
 Matthias
 
I think we should have unicode=yes in rc.conf by default if we have +unicode 
in USE

-- 

Alexey 'Alexxy' Shvetsov
Gentoo/KDE
Gentoo/MIPS
Gentoo Team Ru


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-dev] openrc-0.5.1 arrived in the tree

2009-10-09 Thread Joshua Saddler
On Fri, 9 Oct 2009 19:57:07 +0200
Matthias Schwarzott z...@gentoo.org wrote:

 Hi there!
 
 As some of you have waited long for this to happen, sys-apps/openrc-0.5.1 is 
 there. It has a default enabled (eapi-1) useflag oldnet to install the 
 old-style network scripts called net.*.
 Regardless of this use-flag, the new init-script /etc/init.d/network is
 always installed.
 
 For transition to new-style network script there is something todo I think.
 Unordered list of todos:
 * hotplug? at least udev does explicitly call in net.* scripts
 * New systems should get old or new scripts?
 * does new scripts already can do all that was possible with net.* ?
 
 So far I hope the update does not break any system.
 In case this happens nevertheless open a bug as usual.
 
 Regards
 Matthias
 

As long as this new version is ~arch (and not hardmasked), you also need to 
send some documentation updates for 
http://www.gentoo.org/doc/en/openrc-migration.xml; patches to bugs.gentoo.org, 
Documentation product. This way we in the GDP can take care of keeping the 
guide up-to-date. Thanks.


signature.asc
Description: PGP signature