On 15.03.2015 10:48, Ulrich Mueller wrote:
>> If we want a separate repo/ namespace, we would probably need to
>> consider moving other repositories there -- at least the
>> official ones. Of course, it would be a nice result, having
>> everything hosted on git.g.o as git.g.o/repo/${repo_name}.git
On 14.03.2015 23:25, Robin H. Johnson wrote:
> Trying to explain to a new user that the Portage tree refers to the
> collection of ebuilds used by a PMS-compliant package manager (eg
> Portage) is problematic.
Full ack. Let's limit "portage" to the piece of software, please.
> Questions: 0. Wha
On 27 March 2015 at 10:32, Andreas K. Huettel wrote:
> It would be great to logically separate ebuild repositories (main tree and
> overlays) somehow logically from code, data, ...
>
> How about adding an additional level "repo" for everything that contains
> ebuild trees?
>
> repo/gentoo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> Questions:
> 0. What names for the tree/repository.
> 1. We have some namespaces in Git: proj, dev, priv, data, sites, exp;
> should the tree be in one of those namespaces, a new namespace, or be
> without a namespace? git://anongit.gentoo.org/NEW-
On 03/14/2015 18:25, Robin H. Johnson wrote:
> 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 original
On Thu, Mar 19, 2015 at 8:39 AM, Brian Dolbec wrote:
> It is that ebuild tree that is the core to
> what makes it a gentoo system.
>
I think this is really the heart of your argument and others who feel
"gentoo" is the best name for the repository.
I'm not going to argue against that here. I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, 19 Mar 2015 12:32:41 +0100
Jan Matejka wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On Sat, 14 Mar 2015 22:25:56 +
> "Robin H. Johnson" wrote:
>
> > Questions:
> > 0. What names for the tree/repository.
>
> git://a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Sat, 14 Mar 2015 22:25:56 +
"Robin H. Johnson" wrote:
> Questions:
> 0. What names for the tree/repository.
git://anongit.gentoo.org/portage-tree.git ?
1. afaik everyone is calling it this way already anyway.
2. Since it is hosted directl
On Sat, Mar 14, 2015 at 7:04 PM, 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 se
On 03/15/2015 02:07 AM, Michał Górny wrote:
>
> The name simply must be 'gentoo'.
Agreed: it should match repo_name.
>
> As for the namespace, proj/ makes most sense of the current namespaces.
I agree with this too, but I don't care if we namespace it or make it
top-level.
On 15-03-2015 11:20:45 +0100, Dirkjan Ochtman wrote:
> On Sun, Mar 15, 2015 at 10:48 AM, Ulrich Mueller wrote:
> >> If we want a separate repo/ namespace, we would probably need to
> >> consider moving other repositories there -- at least the official
> >> ones. Of course, it would be a nice resul
On Sun, Mar 15, 2015 at 2:07 AM, Michał Górny wrote:
>
> Instead of trying to emphasize it's the main repository, we ought to
> drop the notion of 'main repository'. That was the goal of all changes
> in Portage, so stop trying to regress for the sake of good ol' times.
>
But, if the goal is to d
Am Samstag, 14. März 2015, 22:25:56 schrieb Robin H. Johnson:
> 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, be
On Sun, Mar 15, 2015 at 11:34 AM, Kent Fredric wrote:
> Outside the context of "Portage", "repo" can mean any git repository of any
> kind, not merely a portage-usable repository.
Yeah, or an RPM repo, or a Mercurial repo... repo as a term is way
overloaded, so use it with care (and qualification
On 15 March 2015 at 21:54, Dirkjan Ochtman wrote:
> . In that vain, "gentoo-base"
> could also work?
>
I like this idea. I was initially toying with "gentoo-overlay" because it
was more specific than "repo" but it didn't float well because the model
was wrong.
"gentoo-base" however kinda works
On Sun, Mar 15, 2015 at 10:48 AM, Ulrich Mueller wrote:
>> If we want a separate repo/ namespace, we would probably need to
>> consider moving other repositories there -- at least the official
>> ones. Of course, it would be a nice result, having everything hosted
>> on git.g.o as git.g.o/repo/${r
> On Sun, 15 Mar 2015, Michał Górny wrote:
> As for the namespace, proj/ makes most sense of the current
> namespaces.
So on gitweb.gentoo.org our main tree would be listed amongst some
200 other proj repositories, between proj/gentoo-wiki-tyrian.git and
proj/proj/gentoolkit.git.
I think it
On 14 March 2015 at 23:30, Manuel Rüger wrote:
> iirc most deb and rpm based distributions use "main" for their central
> repository, so +1 for gentoo-main.
Add me for gentoo-main too.
Diego Elio Pettenò — Flameeyes
https://blog.flameeyes.eu/
> On Sat, 14 Mar 2015, Andreas K Huettel wrote:
>> 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...
Definitely, it should be "gentoo". Without "portage", "x86", or
"gentoo" makes a lot of sense to me. "gentoo-main" works, as well.
Anything with "ebuilds" doesn't make as much as sense to me, since it
also contains profiles, eclasses, etc. In that vain, "gentoo-base"
could also work?
I don't really get the need for this whole namespacing thing, so I'd
prefer
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
* 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
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).
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 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
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
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
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
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
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...
-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
>
-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
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
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 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
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
36 matches
Mail list logo
