-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Feel free to take over and drop me from metadata.xml, if you're
interested:
* app-editors/diakonos
Description: A Linux editor for the masses
* net-wireless/mfoc
Description: Mifare Classic Offline Cracker
* sys-apps/fwts
This is a mostly inconsequential issue, but the Git migration provides
us a chance to make a clean break...
The repository of our ebuilds and the name of the CVS module have been
called gentoo-x86 since the start of Gentoo, because it originally was
only for x86. Here's the very first ebuild added
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
imho,
> Questions:
> 0. What names for the tree/repository.
"gentoo"
(it's also the repo_name)
"portage" doesn't make sense, everything else is too long or potentially
confusing...
> 1. We have some namespaces in Git: proj, dev, priv, data, sit
On Sat, Mar 14, 2015 at 6:25 PM, Robin H. Johnson wrote:
> 0. What names for the tree/repository.
Suggestions:
gentoo-repo
gentoo-repository
gentoo-main
gentoo-repo-main
gentoo-repository-main
> 1. We have some namespaces in Git: proj, dev, priv, data, sites, exp; should
>the tree be in one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03/14/2015 11:34 PM, Andreas K. Huettel wrote:
> imho,
>
>> Questions: 0. What names for the tree/repository.
>
> "gentoo" (it's also the repo_name)
>
> "portage" doesn't make sense, everything else is too long or
> potentially confusing...
>
On 15 March 2015 at 11:37, Rich Freeman wrote:
> Suggestions:
> gentoo-repo
> gentoo-repository
> gentoo-main
> gentoo-repo-main
> gentoo-repository-main
>
Similarly in the "solve confusion as to purpose" for newbies:
gentoo-packages
gentoo-ebuilds
The names would be possibly be incorrect und
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> > proj/gentoo would be fine for me (with the same logic as in the
> > wiki that "Gentoo" is the "main project")
>
> Personally I would find this a bit confusing so I'd prefer a separate
> namespace or no namespace, if going for a separate namespac
Hello all,
I've long considered the -delete argument to find to be widely supported
enough that using it in ebuilds should not be a problem. Indeed, a grep
of the tree shows that it is frequently used, even in eclasses.
I've just noticed that the man page states that it is not present in
the BSD
On Sat, 14 Mar 2015 23:14:57 +
James Le Cuirot wrote:
> On the one hand, it should always be present now, given what I said about
> @system above but on the other hand, if it gets installed as gfind
> then there's no point in pulling it in if you're only going to call
> find.
Just realised m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 14.03.2015 23:37, Rich Freeman wrote:
> On Sat, Mar 14, 2015 at 6:25 PM, Robin H. Johnson
> wrote:
>> 0. What names for the tree/repository.
>
> Suggestions: gentoo-repo gentoo-repository gentoo-main
> gentoo-repo-main gentoo-repository-main
>
Andreas K. Huettel wrote:
> > 0. What names for the tree/repository.
>
> "gentoo"
IMO this is the only really accurate name.
> (it's also the repo_name)
There you go. It already has the name gentoo. :)
> "portage" doesn't make sense, everything else is too long or
> potentially confusing...
ebuilds/gentoo.git
or
ebuilds/gentoo-main.git
Namespacing things in ebuilds/ might be convenient in the future if we
pursue other types of official ebuild repositories.
Calling it "gentoo" makes sense, because the entire tree is what makes
gentoo. But since it's namespaced in ebuilds/ and beca
Jason A. Donenfeld wrote:
> Calling it "gentoo" makes sense, because the entire tree is what makes
> gentoo.
Exactly. And the repo already has this name set in repo_name.
> But since it's namespaced in ebuilds/ and because ebuilds/
> might have other gentoo-official repos too, then perhaps "gent
On 15 March 2015 at 06:34, Andreas K. Huettel wrote:
> imho,
>
>> Questions:
>> 0. What names for the tree/repository.
>
> "gentoo"
> (it's also the repo_name)
Our repo is already named "gentoo", so this makes the most sense.
But I wouldn't mind "gentoo-main" either. But then we should also
chan
On Sat, Mar 14, 2015 at 9:44 PM, Jason A. Donenfeld wrote:
>
> Calling it "gentoo" makes sense, because the entire tree is what makes
> gentoo. But since it's namespaced in ebuilds/ and because ebuilds/ might
> have other gentoo-official repos too, then perhaps "gentoo-main" makes more
> sense.
T
> mr_bones_15/03/09 18:15:22
>
> Modified: package.use.mask
> Log:
> hide the qt5 stuff for yabause for now
>
> [...]
> +# Michael Sterrett (09 Mar 2015)
> +# Mask qt5 support until qt5 is stable so as to not
> +# hold up making yabause stable.
> +games-emulation/yabause qt5
On Sun, 15 Mar 2015 10:04:55 +0800
Ben de Groot wrote:
> On 15 March 2015 at 06:34, Andreas K. Huettel
> wrote:
> > imho,
> >
> >> Questions:
> >> 0. What names for the tree/repository.
> >
> > "gentoo"
> > (it's also the repo_name)
>
> Our repo is already named "gentoo", so this makes the most
Rich Freeman wrote:
> > Calling it "gentoo" makes sense
>
> The thing is, Gentoo is more than a bunch of ebuilds.
Sure, but the gentoo ebuild repo is just a bunch of ebuilds.
Gentoo as name can and should be used elsewhere too of course.
> Certainly they're a HUGE part of Gentoo, but they alone
On Sat, Mar 14, 2015 at 5:56 PM, Peter Stuge wrote:
> Andreas K. Huettel wrote:
>> > 0. What names for the tree/repository.
>>
>> "gentoo"
>
> IMO this is the only really accurate name.
I completely agree (with everything else in this email as well).
On 14 Mar 2015 23:14, James Le Cuirot wrote:
> I've long considered the -delete argument to find to be widely supported
> enough that using it in ebuilds should not be a problem. Indeed, a grep
> of the tree shows that it is frequently used, even in eclasses.
>
> I've just noticed that the man pag
* Andreas K. Huettel schrieb am 14.03.15 um 23:34 Uhr:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
imho,
Questions:
0. What names for the tree/repository.
"gentoo"
(it's also the repo_name)
+1
My furst idea, too.
--
0x35A64134 - 8AAC 5F46 83B4 DB70 8317
3723 296C 6CC
Dnia 2015-03-14, o godz. 22:25:56
"Robin H. Johnson" napisał(a):
> This is a mostly inconsequential issue, but the Git migration provides
> us a chance to make a clean break...
>
> The repository of our ebuilds and the name of the CVS module have been
> called gentoo-x86 since the start of Gento
22 matches
Mail list logo
