On Sun, 16 Aug 2015 09:52:06 -0700
Raymond Jennings 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 reports on them.
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 wrote:
> On Sun, Aug 16
On Sun, Aug 16, 2015 at 9:47 AM, "Paweł Hajdan, Jr."
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 give you a
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 Sat, Aug 15, 2015 at 10:09 PM, Raymond Jennings wrote:
> On Fri, Aug 14, 2015 at 6:16 PM, Ian Stakenvicius wrote:
>>
>> Finally, the gentoo developer quiz -should- still contain questions
>> about ancient stuff. There are still EAPI0 and EAPI2 ebuilds in the
>> tree at least.
>
>
> Why not de
On Fri, Aug 14, 2015 at 6:16 PM, Ian Stakenvicius 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
> >
-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 th
-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 ri
Dnia 2015-08-15, o godz. 09:06:48
Ulrich Mueller 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 shoul
-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 ebuil
> 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,
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 matte
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 t
On 8/15/15 7:35 AM, Michał Górny wrote:
> Dnia 2015-08-15, o godz. 00:05:57
> Johannes Huber 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 EAPI 4
Dnia 2015-08-15, o godz. 00:05:57
Johannes Huber 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
> (< EAP
-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 dec
-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
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 declar
-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 de
19 matches
Mail list logo
