On Sun, Sep 01, 2013 at 08:58:07PM -0400, James Cloos wrote:
> > "TW" == Tom Wijsman writes:
>
> TW> Also, please just call it git-3.eclass as it is a major change; any
> TW> other form of naming will introduce confusion (eg. -r1 < -2), also we
> TW> probably shouldn't change git-2.eclass as
> "TW" == Tom Wijsman writes:
TW> Also, please just call it git-3.eclass as it is a major change; any
TW> other form of naming will introduce confusion (eg. -r1 < -2), also we
TW> probably shouldn't change git-2.eclass as even when masked it doesn't
TW> seem like a good thing to break its cur
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> The new eclass is supposedly used by 732 in-tree packages [1],
> and possibly a few dozens out-of-the-tree. Some parts of the eclass API
> are barely used. I would really prefer to avoid yet another eclass
> migration.
that's a shame, I don't think
On 08/28/2013 10:00 AM, Michał Górny wrote:
>
> What are your thoughts?
>
Not interested in any of those suggestions. git-2.eclass works fine for
me and I will keep using it.
On 28 August 2013 16:00, Michał Górny wrote:
> Hello, all.
>
> I think I'm finally ready to put all the breaking awesomeness that was
> waiting for the git eclasses. However, I'm wondering what's the best
> way of proceeding with it.
>
> We've just lately finished the git->git-2 eclass migration.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/28/2013 10:00 AM, Michał Górny wrote:
> The new eclass is supposedly used by 732 in-tree packages [1], and
> possibly a few dozens out-of-the-tree. Some parts of the eclass
> API are barely used. I would really prefer to avoid yet another
> ecl
> What did you use that for?
Actually, for "--depth 1" in custom non-maintained-already ebuild ;)
signature.asc
Description: OpenPGP digital signature
Dnia 2013-08-28, o godz. 16:31:36
Tom Wijsman napisał(a):
> On Wed, 28 Aug 2013 10:00:07 +0200
> Michał Górny wrote:
>
> > What are your thoughts?
>
> If possible, assuming it is not already possible I would like to see
> support for checking out multiple repositories; that way the patches
> c
On Wed, 28 Aug 2013 10:00:07 +0200
Michał Górny wrote:
> What are your thoughts?
If possible, assuming it is not already possible I would like to see
support for checking out multiple repositories; that way the patches
can simply be obtained from a repository instead of having to
explicitly snap
Dnia 2013-08-28, o godz. 09:01:54
Ian Stakenvicius napisał(a):
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 28/08/13 07:30 AM, Vadim A. Misbakh-Soloviov wrote:
> >> 4. Kill EGIT_MASTER (it's more trouble than benefit),
> >
> > Only if EGIT_BRANCH will stay on it's place.
> >
>
>
Dnia 2013-08-28, o godz. 18:30:06
"Vadim A. Misbakh-Soloviov" napisał(a):
> > 2. Kill EGIT_HAS_SUBMODULES and autodetect submodules,
>
> I'm disagreed. Sometimes submodules, that repo suggests is unneded,
> since they fetches external package, that specified as RDEP.
Then you are using EGIT_HAS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 28/08/13 07:30 AM, Vadim A. Misbakh-Soloviov wrote:
>> 4. Kill EGIT_MASTER (it's more trouble than benefit),
>
> Only if EGIT_BRANCH will stay on it's place.
>
..and work as well as EGIT_MASTER. I've had issues at times trying to
get the branc
> 2. Kill EGIT_HAS_SUBMODULES and autodetect submodules,
I'm disagreed. Sometimes submodules, that repo suggests is unneded,
since they fetches external package, that specified as RDEP.
>
> 3. Kill EGIT_OPTIONS since it limits the possibility of changing eclass
>code,
:-/
> 4. Kill EGIT_MA
Michał Górny writes:
> I think I'm finally ready to put all the breaking awesomeness that was
> waiting for the git eclasses. However, I'm wondering what's the best
> way of proceeding with it.
TL;DR any futher, but I have few packages which use git-2 eclass and I
wouldn't like to have any break
Hello, all.
I think I'm finally ready to put all the breaking awesomeness that was
waiting for the git eclasses. However, I'm wondering what's the best
way of proceeding with it.
We've just lately finished the git->git-2 eclass migration. The old
eclass is no longer used and is marked for removal
15 matches
Mail list logo
