On Sat, Aug 15, 2015 at 10:09 PM, Raymond Jennings shent...@gmail.com wrote:
On Fri, Aug 14, 2015 at 6:16 PM, Ian Stakenvicius a...@gentoo.org wrote:
Finally, the gentoo developer quiz -should- still contain questions
about ancient stuff. There are still EAPI0 and EAPI2 ebuilds in the
tree
On 8/16/15 3:29 PM, Rich Freeman wrote:
They are deprecated already:
https://gitweb.gentoo.org/repo/gentoo.git/tree/metadata/layout.conf
Deprecated means stop adding them, and move away from them. Repoman
will give you a warning about them.
Is anything blocking deprecating EAPI4 in the
On Sun, Aug 16, 2015 at 9:47 AM, Paweł Hajdan, Jr.
phajdan...@gentoo.org wrote:
On 8/16/15 3:29 PM, Rich Freeman wrote:
They are deprecated already:
https://gitweb.gentoo.org/repo/gentoo.git/tree/metadata/layout.conf
Deprecated means stop adding them, and move away from them. Repoman
will
What's the best way to get rid of deprecated ebuilds?
Do we just wait for their maintainers to migrate them or should they be
sought out and flagged? I'm pondering searching for EAPI 0 ebuilds and
filing bug reports on them.
On Sun, Aug 16, 2015 at 6:57 AM, Rich Freeman ri...@gentoo.org wrote:
On Sun, 16 Aug 2015 09:52:06 -0700
Raymond Jennings shent...@gmail.com wrote:
What's the best way to get rid of deprecated ebuilds?
Do we just wait for their maintainers to migrate them or should they
be sought out and flagged? I'm pondering searching for EAPI 0
ebuilds and filing bug
On Fri, Aug 14, 2015 at 6:16 PM, Ian Stakenvicius a...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/08/15 06:43 PM, Johannes Huber wrote:
Am 08/15/15 um 00:19 schrieb Andrew Savchenko:
Hi,
While I have no objections about EAPI 4 deprecation (except
On Sat, 15 Aug 2015, Paweł Hajdan, wrote:
Nothing seems to prevent doing the mass conversion first,
deprecating EAPI 4, and then having a second, slower pass to make
sure the ebuilds are using EAPI 5 as they should be. One way might
be to add a TODO comment during mass conversion, which then
Dnia 2015-08-15, o godz. 09:06:48
Ulrich Mueller u...@gentoo.org napisał(a):
On Sat, 15 Aug 2015, Paweł Hajdan, wrote:
Nothing seems to prevent doing the mass conversion first,
deprecating EAPI 4, and then having a second, slower pass to make
sure the ebuilds are using EAPI 5 as they
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/14/2015 03:05 PM, Johannes Huber wrote:
Hello Gentoos Penguins,
if we want to attract more contributors we should consider to have
one supported EAPI (latest). EAPI 4 is the last not marked as
deprecated ( EAPI 5). The move in ebuilds
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am 08/15/15 um 07:35 schrieb Michał Górny:
This is a cheap hack, not a conversion. Proper conversion to a new
EAPI is about using the new EAPI features. Not marking it 'done',
and pretending there's nothing more to do.
Yeah you are right.
On Sat, 15 Aug 2015 08:12:42 +0200 Paweł Hajdan, Jr. wrote:
On 8/15/15 3:16 AM, Ian Stakenvicius wrote:
Secondly, though, conversion to EAPI5 is not actually trivial, there
are a couple of things, 'usex' related for instance, that also need
to be taken care of. If it was just a matter of
On 8/15/15 3:16 AM, Ian Stakenvicius wrote:
Secondly, though, conversion to EAPI5 is not actually trivial, there
are a couple of things, 'usex' related for instance, that also need
to be taken care of. If it was just a matter of running a sed -e
's/^EAPI=4/EAPI=5/' on all in-tree ebuilds this
On 8/15/15 7:35 AM, Michał Górny wrote:
Dnia 2015-08-15, o godz. 00:05:57
Johannes Huber j...@gentoo.org napisał(a):
if we want to attract more contributors we should consider to have one
supported EAPI (latest). EAPI 4 is the last not marked as deprecated
( EAPI 5). The move in ebuilds from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15/08/15 02:48 AM, Andrew Savchenko wrote:
On Sat, 15 Aug 2015 08:12:42 +0200 Paweł Hajdan, Jr. wrote:
On 8/15/15 3:16 AM, Ian Stakenvicius wrote:
Secondly, though, conversion to EAPI5 is not actually
trivial, there are a couple of things,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Gentoos Penguins,
if we want to attract more contributors we should consider to have one
supported EAPI (latest). EAPI 4 is the last not marked as deprecated
( EAPI 5). The move in ebuilds from EAPI 4 to EAPI 5 is very simple
replacing the
Hi,
On Sat, 15 Aug 2015 00:05:57 +0200 Johannes Huber wrote:
if we want to attract more contributors we should consider to have one
supported EAPI (latest). EAPI 4 is the last not marked as deprecated
( EAPI 5). The move in ebuilds from EAPI 4 to EAPI 5 is very simple
replacing the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am 08/15/15 um 00:19 schrieb Andrew Savchenko:
Hi,
While I have no objections about EAPI 4 deprecation (except
concerns mentioned above), I see no strong need for this also. Just
declare EAPI 5 as recommended. Having legacy support for EAPI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/08/15 06:43 PM, Johannes Huber wrote:
Am 08/15/15 um 00:19 schrieb Andrew Savchenko:
Hi,
While I have no objections about EAPI 4 deprecation (except
concerns mentioned above), I see no strong need for this also.
Just declare EAPI 5
Dnia 2015-08-15, o godz. 00:05:57
Johannes Huber j...@gentoo.org napisał(a):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Gentoos Penguins,
if we want to attract more contributors we should consider to have one
supported EAPI (latest). EAPI 4 is the last not marked as deprecated
19 matches
Mail list logo
