Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
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. What names for the tree/repository.
It's not a tree. Ideally, it would be a directed acyclic graph (DAG),
there maybe be some loops, even.
I would therefore object to any name that has tree in it.
Since there are other Gentoo-based distros, I would say the word
gentoo should be in there.
Plain gentoo may work. I would be happy with any of
gentoo-{core,main,master} as well, if plain gentoo causes trouble
for a name in some context.
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-NAME.git.
Not in any of those namespace, please.
If in any, make it repos or repositories, please.
Thanks for your consideration.
Best,
Sebastian
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
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.
Isn't repo fairly redundant? Everything there is a repository.
There are Git repositories that do not contain ebuilds up there. So
repo is not redundant if it refers to its overlays kind of meaning.
Two examples:
http://gitweb.gentoo.org/proj/portage-utils.git/
http://gitweb.gentoo.org/proj/userinfo-scripts.git/
Best,
Sebastian
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
-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-NAME.git. Here's an additional suggestion. 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 -- our main tree repo/proj/kde repo/proj/perl-overlay repo/dev/dilfridge Everything else stays where it is, eg., data/glsa proj/sandbox proj/portage ... - -- Andreas K. Huettel Gentoo Linux developer (council, perl, libreoffice) dilfri...@gentoo.org http://www.akhuettel.de/ -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJVFHriAAoJEB9VdM6hupKVFbQQAK8xxy0TKMR9/a56ZTjgjZZE g/a2KqcwGuCRRkgGRHeRMiC5kkh8L1mS9WBJNIYA05todRv2eqG9fQCzO0xhF0YK iOMqBtO8A+KCgGcJ6ilaaCUn1Lp62d7bqdXvePE0i98qVrc1rXeXJGTAk4J/jGPQ 95iShF1/Pe8GGxJ/Qw+ekOwoDgqBCVJzjBEedfoOzI5yqxXDJZR1nCBqzZwl7DhW Fe/GQvNtTlGSlVq5i/1aOfVekabIGR82P+nqzSyKF88aYTdDVrmmeszvMx/pHOmk sdA8/k1JWNahK3RwL2n8xvil0sKFzPGiIqrV6VLJj5FnF+85ZSy4WYKuI4mJUQmx Nb3hELnZYs+J9COH7vGaHVGnVfZonkRm1AuTmzkDv2nBp92Z37DRA6m5vGlik9a7 rD02omjBaEJXZovxHOP30RlIxxqo5g0V2ytdqh8gD8sOsn21CGKJc/9QqzQ8SjrG tqQPwM+O0Kqk5Vl8CAuqm9J4cnJJSwoO7g1ERjv2y4zW4o7sQgMBdiNQ1w/It0q5 FjXK6x+8zB3jyKKkFQX70FQwjgDMlwYdEizbTKmRImeHDD7HUclOcC1NurrZNpS4 KwSFeNDiJ/4yslRCWXpgf5AJRszqQ7D0KOTlqiEOySsXuTc12ChPot143XILRCCB Uu7WG42KljBVR/zKIFrR =QmjZ -END PGP SIGNATURE-
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
On 27 March 2015 at 10:32, Andreas K. Huettel dilfri...@gentoo.org 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 -- our main tree repo/proj/kde repo/proj/perl-overlay repo/dev/dilfridge Everything else stays where it is, eg., data/glsa proj/sandbox proj/portage ... Agreed. It used to imply overlays by being called 'git.overlays.gentoo.org'. But but now its just going to be 'git.gentoo.org' And there's proj/ which is frankly dogs breakfast. Re-organising that to be sensible is a bit much to ask at this time. But maybe gentoo can at least start the ball rolling. -- Kent *KENTNL* - https://metacpan.org/author/KENTNL
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
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 originally was only for x86. Here's the very first ebuild added to CVS [1], Portage v1.1 is also early on [2]. On the rsync side, it was originally called gentoo-x86-portage, and then between the 1.2 and 1.4 release (early 2003), the stages switched to using the name 'gentoo-portage'; as recently as 2010, various mirrors were STILL fetching from the name of gentoo-x86-portage, when we reminded them that they should have switched years ago. All of these names have caused some confusion. 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. To that end, I'd like us to brainstorm names for the new bikeshed^R^R^R^R^R^R^R^R repository, to go live at the time of the Git migration. It will be the single tree that contains what you find today in the gentoo-x86 CVS module; and on rsync as gentoo-x86-portage and gentoo-portage. Ideally, it should be something that works as a relatively unique identifier (Portage is bad as it refers to both the package manager and the tree), and fits easily into discussions, both in-person and online. 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-NAME.git. [1] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-mail/mutt/mutt-1.2.5-1.ebuild?hideattic=0revision=1.1view=markupsortby=date [2] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-apps/portage/files/ebuild?hideattic=0revision=1.1view=markupsortby=date#l1051 I'm going to march to the beat of a different drummer and suggest we keep it as gentoo-portage. That's probably the old developer/luddite in me talking, but regardless of whatever the future name is, I'm probably always going to call it the portage tree, because that's all I've ever known it as. I guess if I *had* to choose a new name, the following variations come to mind (kinda in no particular order): pkgtree gentoo-pkgtree ptree gentoo-ptree the-tree trunk core -- Joshua Kinard Gentoo/MIPS ku...@gentoo.org 4096R/D25D95E3 2011-03-28 The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between. --Emperor Turhan, Centauri Republic
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Sat, 14 Mar 2015 22:25:56 + Robin H. Johnson robb...@gentoo.org 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 directly on gentoo.org/ there should be no need to further qualify it's The portage tree. - -- Jan Matějka| Developer https://gentoo.org | Gentoo Linux GPG: A33E F5BC A9F6 DAFD 2021 6FB6 3EBF D45B EEB6 CA8B -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCgAGBQJVCrPZAAoJEIN+7RD5ejahX9sH/iZ89zzs+/9AMtQJAeF1vVOK QehdJzsdysM8TqI3kzpoHvFkFw8IXp54pnckcPyiNwJFjsMFP4R+uOGqoYskaCnm SCX3ovm/sgHY6tscCEfaqFtrzRK/Nt0ESG7Gyz+RVtBU75CcZT0YviCB2MBOYdag d7hONjPhOK0i6dHeocf1321Oi40P2XPqU2wepKpLhc8zcAGczDdYisDUcFwWH/m2 fVizZZmpJYdu6ecNCHNYOm/D+BY37BsHeoHzDC+0Tt/F7IseDQZFmy6Xbgm4fHf+ dkjTBl5N8zF/sdOiuXxPJBr/g/yZ0rrOJWolG5ZZeObUra+TpAUmH4R/y6QZLx4= =CUHS -END PGP SIGNATURE-
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Thu, 19 Mar 2015 12:32:41 +0100 Jan Matejka y...@gentoo.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Sat, 14 Mar 2015 22:25:56 + Robin H. Johnson robb...@gentoo.org 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 directly on gentoo.org/ there should be no need to further qualify it's The portage tree. - -- Jan Matějka| Developer https://gentoo.org | Gentoo Linux NO, NOT a chance... It's already been said that it makes it too often confused with portage the package manager. Plus there are 2 other package managers that work with that tree. It is that ebuild tree that is the core to what makes it a gentoo system. AND the current repo_name is gentoo which many tools already expect it to be. SO the logical choice is for it to remain called gentoo. But as far as the git repo is concerned, it can be a variation of that and still be cloned into a 'gentoo' subdirectory for on disk use as the main tree. be it gentoo-ebuilds, ebuilds/gentoo, trees/gentoo, repos/gentoo,... The directory name it is installed to MUST be the same as it's repo_name. $ git clone git://anongit.gentoo.org/gentoo-tree.git gentoo The rsync tree generated from the git repo must also be set to clone into a gentoo named directory. - -- Brian Dolbec dolsen -BEGIN PGP SIGNATURE- Version: GnuPG v2.0 iQJ8BAEBCgBmBQJVCsOZXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNUQ3Qzc0RTA4MUNDNzBEQjRBNEFBRjVG QkJEMDg3Mjc1ODIwRUQ4AAoJEPu9CHJ1gg7YtakQAIX1AUaIoQHUvSfCkXKLYZjw bSoMun0l+4RWFgh4n7tCq2gIGLhilZYXZZEuhj4LWaQE0GiGZMc262DJM/+6Ja8i HtN3NB1fHb/bhC7mujp2p8cG2Rkw3va5215CEUa48tIUPciYXqS0+MIquTL10hrl ga8oggv+cMWU8nECSpKUvmWTGC2SqyAU4vvpMBUYPMqGVkckurREed8peVAnGATw ySwpZrSpqLu4EUVLlm4Y+jDA84Si0YHIVeoLUXhRqJFRBk98tmmNqnQT86YYNjMn juNb+LNKiZ/Q+Mcr08tS/rR+9zwGq7gFhtA5T0s4K5KdU5cD5/+slpGi4sKOND6C IsjNZTUASc2/WjBVqbi4YfYHPEi6c2oo0hOr+gHSfYK5hvQdBjs9xNoMPYesLCuv EN+hWym7T9JaU8dW2K+5eK/y8lYMzFUB+snSILWjkGHVO3kRWIAQTiAdJUcTQ1e+ O/vcABryy5kTOzb2vwItTQn1lKnOEFLBk0EE5tUhSyt9qmzF6YRsBuKdy61Q6oDk Q2zZrUfHorApkY1+WA+Z72Nl+lO/0V/50XJxQ456ES9QnyrvoyQODhDjqlNIt3ko XB2srPbaARW9S9bBJNcy747/eJfH8dxK61GHhEf6jGpf7AtKwKEs6PeJwK/3uj41 EIIW+QbVaReK0cu4YfWA =42cr -END PGP SIGNATURE-
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
On Thu, Mar 19, 2015 at 8:39 AM, Brian Dolbec dol...@gentoo.org 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 not convinced that Gentoo is just the ebuild tree, but you're not really saying that. Is there a good reason not to call the repository gentoo and leave it at that? Are there other source repositories that are also key to Gentoo such that such a generic name would cause confusion? I think the biggest argument against this is that a Gentoo install is a compilation of many Gentoo projects, of which the ebuild tree is a key and unifying one, but it also includes stuff like the install media, stage3, openrc/baselayout, maybe eudev, and usually portage/emerge. Is there more to it than this? Is there a new argument we haven't already heard? I just want to make sure all the perspectives are out there before a call gets made. -- Rich
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
On 14 March 2015 at 23:30, Manuel Rüger mr...@gentoo.org 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/
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
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.
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
On 15-03-2015 11:20:45 +0100, Dirkjan Ochtman wrote:
On Sun, Mar 15, 2015 at 10:48 AM, Ulrich Mueller u...@gentoo.org 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.
Isn't repo fairly redundant? Everything there is a repository.
Everything is a git repo, but not everything is an ebuild/Portage
repo... Which is another point against the use of repo in any
Portage-specific way.
tree/gentoo
tree/prefix
... ?
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: Digital signature
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
On Sun, Mar 15, 2015 at 2:07 AM, Michał Górny mgo...@gentoo.org 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 drop the notion of main repository why would we name it Gentoo - as if leaving it out makes it no longer Gentoo? Is it Gentoo without what we now call gentoo-x86? If not, then I don't get the objection to the term main repository since that is what it basically is then. I don't feel super-strongly about this. I just am not sure that your suggestion actually promotes the goals you seem to want to promote. -- Rich
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
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 deserves a more prominent place.
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.
Isn't repo fairly redundant? Everything there is a repository.
Ulrich
pgpjme4Zuq0dF.pgp
Description: PGP signature
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
On Sun, Mar 15, 2015 at 10:48 AM, Ulrich Mueller u...@gentoo.org 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.
Isn't repo fairly redundant? Everything there is a repository.
Everything is a git repo, but not everything is an ebuild/Portage
repo... Which is another point against the use of repo in any
Portage-specific way.
Cheers,
Dirkjan
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
On 15 March 2015 at 21:54, Dirkjan Ochtman d...@gentoo.org 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 in the vein of This is the base the other overlays are applied to. But YMMV =). Isn't repo fairly redundant? Everything there is a repository. Everything is a git repo, but not everything is an ebuild/Portage repo... Which is another point against the use of repo in any Portage-specific way. This also is my problem. Its fine to say gentoo in the repo itself, because it can assume from the consuming context that given a set of portage repositories, the one with the name gentoo is the gentoo portage repository. But without that context, in a context where there are repos that are *not* portage repositories, I feel there should be some sort of qualifier to disambiguate between general project repositories ( e.g. : the source code for portage itself ) and collections of ebuilds and supporting files, which are all known as repos ... but they're only repos with in the context of Portage. Outside the context of Portage, repo can mean any git repository of any kind, not merely a portage-usable repository. -- Kent *KENTNL* - https://metacpan.org/author/KENTNL
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
Dnia 2015-03-14, o godz. 22:25:56
Robin H. Johnson robb...@gentoo.org 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 Gentoo, because it originally was
only for x86. Here's the very first ebuild added to CVS [1], Portage
v1.1 is also early on [2].
On the rsync side, it was originally called gentoo-x86-portage, and then
between the 1.2 and 1.4 release (early 2003), the stages switched to
using the name 'gentoo-portage'; as recently as 2010, various mirrors
were STILL fetching from the name of gentoo-x86-portage, when we
reminded them that they should have switched years ago.
All of these names have caused some confusion. 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.
To that end, I'd like us to brainstorm names for the new
bikeshed^R^R^R^R^R^R^R^R
repository, to go live at the time of the Git migration.
It will be the single tree that contains what you find today in the
gentoo-x86 CVS module; and on rsync as gentoo-x86-portage and
gentoo-portage.
Ideally, it should be something that works as a relatively unique
identifier (Portage is bad as it refers to both the package manager and
the tree), and fits easily into discussions, both in-person and online.
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-NAME.git.
The name simply must be 'gentoo'. If you think it's easy to change
repo_name, think again. That name is hardcoded in a lot of random
places (like Portage configuration, databases), and it is used by some
external tools as a replacement of deprecated PORTDIR. Not to mention
all overlays.
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.
As for the namespace, proj/ makes most sense of the current namespaces.
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.
--
Best regards,
Michał Górny
pgp7UMTnWnpuU.pgp
Description: OpenPGP digital signature
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
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 to do without that. Cheers, Dirkjan
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
On Sun, Mar 15, 2015 at 11:34 AM, Kent Fredric kentfred...@gmail.com 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). Cheers, Dirkjan
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
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 any other suffixes. 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-NAME.git. Keep it at top level, without a namespace. This will also result in the shortest URI. proj/gentoo would be fine for me (with the same logic as in the wiki that Gentoo is the main project) We shouldn't base our decisions on technical limitations of the wiki. Gentoo is not a project in the sense of GLEP 39. Ulrich pgpkqriqiE16G.pgp Description: PGP signature
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
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, because it originally was only for x86. Here's the very first ebuild added to CVS [1], Portage v1.1 is also early on [2]. On the rsync side, it was originally called gentoo-x86-portage, and then between the 1.2 and 1.4 release (early 2003), the stages switched to using the name 'gentoo-portage'; as recently as 2010, various mirrors were STILL fetching from the name of gentoo-x86-portage, when we reminded them that they should have switched years ago. All of these names have caused some confusion. 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. To that end, I'd like us to brainstorm names for the new bikeshed^R^R^R^R^R^R^R^R repository, to go live at the time of the Git migration. It will be the single tree that contains what you find today in the gentoo-x86 CVS module; and on rsync as gentoo-x86-portage and gentoo-portage. Ideally, it should be something that works as a relatively unique identifier (Portage is bad as it refers to both the package manager and the tree), and fits easily into discussions, both in-person and online. 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-NAME.git. [1] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-mail/mutt/mutt- 1.2.5-1.ebuild?hideattic=0revision=1.1view=markupsortby=date [2] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-apps/portage/fi les/ebuild?hideattic=0revision=1.1view=markupsortby=date#l1051 My proposal would be: gentoo-core Greetings -- Johannes Huber (johu) Gentoo Linux Developer / KDE Team GPG Key ID F3CFD2BD signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
On Sat, Mar 14, 2015 at 7:04 PM, Ben de Groot yng...@gentoo.org wrote:
On 15 March 2015 at 06:34, Andreas K. Huettel dilfri...@gentoo.org
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
change the repo_name.
While we are at it, can we change the default location from
/usr/portage to something like /var/repos/${repo_name} then?
I think coupling the two changes is a pretty bad idea. Doubly so since
people have been trying to change the default for years without success.
Lets just get this one thing done and not couple it.
-A
--
Cheers,
Ben | yngwin
Gentoo developer
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
-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 robb...@gentoo.org 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 of those namespaces, a new namespace, or be without a namespace? git://anongit.gentoo.org/NEW-NAME.git. I'd suggest creating a repository(-ies) namespace (or maybe call it repo(s)), since conceivably we might have more than one at some point, overlays might end up in there at some point, etc. iirc most deb and rpm based distributions use main for their central repository, so +1 for gentoo-main. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0 iQJ8BAEBCgBmBQJVBMSUXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4MDA1RERERkM0ODM2QkE4MEY3NzY0N0M1 OEZCQTM2QzhEOUQ2MzVDAAoJEFj7o2yNnWNcIW4P/RLzP0OhM6SpFbCPvXRNbIqJ ggL/BXHY7G6xOO++CHxIvNx00cLtoK0lq0MANBbjNffQ5Wv/LHxhrF2oX4CwO91a AYwZEkmtaauLkx8xrVmhFvuq/liPD4So1JMZ/HMomMa1yb2VevPMjSXW2YwimnM4 wADziajFGcdJR+yXkv3agl/mLC+vugGRlkMTDBXbwVG9qyhI+8Lmgup7UNerikKB Rz+oOzGuAxm35B/WqEHN1okME2WLce7sK1iCUfHscgPAuyz3tbB7B3VuDMLtyisL lDo3IOroI5Xug1u0+dABmuGgEeWb1GsZH059E05dmRMoEicyimFmwAw0YTfmqP0k /e4QhMiEX4xB8GnASByWSAMPR5cDd5FzS1nImcE6Vm/3PfPhWwdFhAWk5irna3iw dzQ4SGt0HH6G5EQKPSFtCkNYOfDDzXNCWFPwDzyppkr0NdpR0vmLOK8ZNW/RiSMJ Rqmsghbecp/ISx+Df1fEnOrOtZY+8NwnyWbe2kVDJnUaxRXnqmm7Jydn1kL0v1dC b9g87wBdMzxR1Wa1qA0elhbR5V8x89XTflrJAzSO+Q7NTEDfnsUTQnbKEMMNIEwT halUzQ3ztbVErZ/pedP4a3zY0VgIMPECFo9aFcJz6zYZUtD+QImNQMyRu3Llibc6 erviQ5ymtEymKsoOSVn0 =Ju4K -END PGP SIGNATURE-
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
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... Yes indeed. Rich Freeman wrote: 0. What names for the tree/repository. Suggestions: gentoo-repo gentoo-repository gentoo-main gentoo-repo-main gentoo-repository-main These are all terribly long and fairly redundant. 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-NAME.git. I'd suggest creating a repository(-ies) namespace (or maybe call it repo(s)), since conceivably we might have more than one at some point, overlays might end up in there at some point, etc. This is a good point. repos/gentoo.git or maybe ebuilds/gentoo.git Kent Fredric wrote: Similarly in the solve confusion as to purpose for newbies: Please be careful to avoid creating simple names for things which are actually more complicated than a simple name can express accurately. That only creates even more confusion. Names need to be accurate and short. It's very difficult to find the right ones and it is an important matter. gentoo-packages No way, packages in Gentoo are .tbz2 files, not .ebuild files. Other distributions already confuse the naming of their packages with the files used to create the packages. Gentoo does not need to be that stupid. gentoo-ebuilds An ebuilds namespace may not be such a bad idea, especially if later on there will be more ebuild repos next to the gentoo one. Manuel Rüger wrote: iirc most deb and rpm based distributions use main for their central repository, so +1 for gentoo-main. Gentoo is significantly different from simple binary distributions - let's not create unneccessary problems by copying their sillyness. Thanks //Peter
[gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
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 to CVS [1], Portage v1.1 is also early on [2]. On the rsync side, it was originally called gentoo-x86-portage, and then between the 1.2 and 1.4 release (early 2003), the stages switched to using the name 'gentoo-portage'; as recently as 2010, various mirrors were STILL fetching from the name of gentoo-x86-portage, when we reminded them that they should have switched years ago. All of these names have caused some confusion. 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. To that end, I'd like us to brainstorm names for the new bikeshed^R^R^R^R^R^R^R^R repository, to go live at the time of the Git migration. It will be the single tree that contains what you find today in the gentoo-x86 CVS module; and on rsync as gentoo-x86-portage and gentoo-portage. Ideally, it should be something that works as a relatively unique identifier (Portage is bad as it refers to both the package manager and the tree), and fits easily into discussions, both in-person and online. 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-NAME.git. [1] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-mail/mutt/mutt-1.2.5-1.ebuild?hideattic=0revision=1.1view=markupsortby=date [2] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-apps/portage/files/ebuild?hideattic=0revision=1.1view=markupsortby=date#l1051 -- Robin Hugh Johnson Gentoo Linux: Developer, Infrastructure Lead E-Mail : robb...@gentoo.org GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 signature.asc Description: Digital signature
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
-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 namespace it might allow for sub-trees down the road, etc... Correct, sorry, I completely over-read that. No namespace, top level would really be best. We only have one main tree!!! - -- Andreas K. Huettel Gentoo Linux developer dilfri...@gentoo.org http://www.akhuettel.de/ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0 iQJ8BAEBCgBmBQJVBLmaXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQwNzlCRDk4QzA4RENBRkYzQUEwRjQzMDlF QkU2QTMzNkJFMTkwMzlDAAoJEOvmoza+GQOcsZsQAN1X/2rwh/C5g6Hgisza9p0K 79AnaAW5mqunO6LWUtlzowBXvzneiXy3Hp8i7g7H09qRTuWMBnLTiUMErkE6pPxt dCSMogiLyAx5NaWmB6BBbrZqrCz529/3jQD5lUL/SIBOXJzSBBLsbJ8NBMrLYHl5 +jre5FYgje/rEpyZUNU3tlmmB6BCSNXEFPHWYMHkvWmwE+Z2lAMLUAAYUT24SJ3X HyAxznn+NHL7N/RbW8rbhw4pjlis+DZFoHSfAtavdsxY0jleRWA9AHq/xDG9Chez tK6ilISITfQU6bTpan/ogX9cRSzrn1KTagEV2JiBSF8214IB3z/v8FMUPadDaPzk XvYacw34yfot2lsO8W6zjXdnunknJ5VZInuzF336D50jH7ihHVdDPm4vM/Ku6t3B WOP7aLZT6+6o4AuobrvQopoiNj5EZW957pRpnmlDeSEqBNLYlUk1uZJvhHzQXmDP 61vkKO1PRINu8THwSEwiFQpRmvV8ZTCpjgMIfIzqsZQzuzY5t9d2VPXVBSghxCE/ 9xZg6ahpkcBgxGp5JhB4hdVZi3CYXxNXDeq5yJEe3HTICAqg2CPLBVfWEOurJxHJ lNw9BV8mFQvEqm1KkPLiWnjyHz5+9rXPrkk9Vb2+GrgMJIBsU3/tyl27BYMKhGbT lPcW5oGlb7D6k1e3UP0P =ypEe -END PGP SIGNATURE-
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
On 15 March 2015 at 06:34, Andreas K. Huettel dilfri...@gentoo.org 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
change the repo_name.
While we are at it, can we change the default location from
/usr/portage to something like /var/repos/${repo_name} then?
--
Cheers,
Ben | yngwin
Gentoo developer
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
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 gentoo-main makes more sense. If ebuilds/ only has gentoo-official repos then leading gentoo- is repetitive and redundant, and unlike gentoo simply main is a horrible name. //Peter
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
On 15 March 2015 at 11:37, Rich Freeman ri...@gentoo.org 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 under some interpretations, but they'd be clearer to newbies what its for. You could consider a repository to be A collection of packages, and all files that are not packages to be metadata. -- Kent *KENTNL* - https://metacpan.org/author/KENTNL
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
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 because ebuilds/ might have other gentoo-official repos too, then perhaps gentoo-main makes more sense.
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
On Sat, Mar 14, 2015 at 9:44 PM, Jason A. Donenfeld zx...@gentoo.org 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. The thing is, Gentoo is more than a bunch of ebuilds. Certainly they're a HUGE part of Gentoo, but they alone aren't Gentoo. In some sense you could have ebuilds/gentoo.git but then what happens when you clone ebuilds/gentoo.git, website/gentoo.git, and so on? Namespaces are useful to prevent accidental collisions, and for organization, but without getting too crazy with the names I think it is best off when the final name stands on its own reasonably well. It doesn't have to be gentoo-main, but I would prefer to see it not just be Gentoo. -- Rich
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
On Sat, Mar 14, 2015 at 6:25 PM, Robin H. Johnson robb...@gentoo.org 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 of those namespaces, a new namespace, or be without a namespace? git://anongit.gentoo.org/NEW-NAME.git. I'd suggest creating a repository(-ies) namespace (or maybe call it repo(s)), since conceivably we might have more than one at some point, overlays might end up in there at some point, etc. -- Rich
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
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 aren't Gentoo. In some sense you could have ebuilds/gentoo.git but then what happens when you clone ebuilds/gentoo.git, website/gentoo.git, and so on? Keep them in different subdirectories, to reflect the central namespace? Namespaces are useful to prevent accidental collisions, and for organization, but without getting too crazy with the names I think it is best off when the final name stands on its own reasonably well. Always optimize for the common case. What changes more often, ebuilds/ or website/ ? That repo gets to use the pretty name, the other repo gets an uglier one, maybe website/website.git. :) //Peter
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
* 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 6CCA 35A6 4134 signature.asc Description: Digital signature
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
-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, sites, exp; should the tree be in one of those namespaces, a new namespace, or be without a namespace? git://anongit.gentoo.org/NEW-NAME.git. proj/gentoo would be fine for me (with the same logic as in the wiki that Gentoo is the main project) alternatively a separate namespace, but how to name it? cheers, andreas - -- Andreas K. Huettel Gentoo Linux developer dilfri...@gentoo.org http://www.akhuettel.de/ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0 iQJ8BAEBCgBmBQJVBLdhXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQwNzlCRDk4QzA4RENBRkYzQUEwRjQzMDlF QkU2QTMzNkJFMTkwMzlDAAoJEOvmoza+GQOch0EP/2HxIk0+k0/7G63BplNZLVvt Rm9sH/q/RRL6IWLlPNGnw+aMtmN1hL2kLJDGnzn6vrimpRqnlWD64dadVSD0IEOY 91JHN5y0XJpeS6UDKl9ibyjDQ/DYPDNGPjbi7r1TLtT1nc6z4prADfwedNizKYax 4rLck9G+VzhO++zrdPPN/3vNKnAet6WLUmzt1HDYeYIRsekWTXtnYFbtaEPmytPi 43V3j/qGKw5FAJIBpG2QwppM8+iGWxUwXNOCCjPJ2wE1W+vcYVaw0We9hKWdqbCP x80MsYb8z3cEQhxscdQiNhWDUSQ1wB43pQHsTTCkdaNbUWDqIsE87G/7b0BjTAzf WqSHWTeGTHAG24xyTOoTngwoSNhsdiLQ13cGPxtNSCUMzgvSb0/W5dhmoMX9/mEy 8vHuhXiBuYxahkxEXhWn0NI13s2IW4RsO1rS452tSWm4a0llX1cT+Cl304eoi8eS wGsuqvjsNXEB1BBf3oAga8nnGbtsvmyzRiclHF2mpb6jy2KKDOEt1PhaVvJG8g7p OoKq1wUDpWJ5BfnI08zy8Lj/48Gf3/TDedTerAWWJo7cYmDUDctRI7YgxIOF8Boh bZFmyy7MaSzdFNnvtNDtilPW09v54RWRn3Okb6luXMuP5k1brc7lgWO77I7wZB1T QZJcU6xdr8BFCJdCd0nD =zyaw -END PGP SIGNATURE-
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
-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... 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-NAME.git. 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 namespace it might allow for sub-trees down the road, etc... alternatively a separate namespace, but how to name it? maybe repos or tree? - -- Kristian Fiskerstrand Public PGP key 0xE3EDFAE3 at hkp://pool.sks-keyservers.net fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 -BEGIN PGP SIGNATURE- iQEcBAEBCgAGBQJVBLhoAAoJEP7VAChXwav6afUH/Ao6oxTeZuKN4x5xYlBOTwOL gWhnHW7yhQ41toi13EAQn8WtKSJdtJIuz81MxXL0AnUFfdspjOZBRfExgkoIUrto EsOAEcrmucPJmO4S2k8WQmg1aFwd9EXzG+Raw8x5x5jQONmufCxI/g6H2RgULqfm F3XKtc2+a3lHWtfmqcmEq7nsS5QBD7HXdN2CBaHkk3J6p0pJ1B6qSkVT8FdBhuJT Q4WHlvvHxg69Ungc9RIGDWp9dDQFpo68zG/A8jXCw4bUgX3zLlE/QOVNAFSsEYOT Gdxr5kEarOedZdIeLfF0OAQIbaeYSkclarO4F4E3BXFgHfA+bm5KwDnhgaFUqQ0= =TRCu -END PGP SIGNATURE-
Re: [gentoo-dev] Naming of repositories: gento-x86 edition, bike shedding wanted
On Sat, Mar 14, 2015 at 5:56 PM, Peter Stuge pe...@stuge.se 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).
