1 |
<marco <at> nucleus.it> writes: |
2 |
|
3 |
|
4 |
> I have a profile for my config , additional ebuilds , packages etc but |
5 |
> i'm looking for the best way to have a production-profile and a |
6 |
> devel-profile. |
7 |
|
8 |
Your not alone. |
9 |
|
10 |
> Better have two separeted git , one for production and one for devel ? |
11 |
> or better one git and use branch functions ? |
12 |
|
13 |
Good question. |
14 |
|
15 |
> With Layman and two git repo i can sync each repo when i want and i can |
16 |
> enable/disable one of them to switch from/to production/devel . |
17 |
|
18 |
> I don't know how to do that directly with git. |
19 |
|
20 |
OK, so I have mentioned the need for a structured (preferred or suggested) |
21 |
pathway for users to use git, in all of the common needs, the gentoo-way. |
22 |
Aka, a document or collection of docs in the gentoo-wiki, related to common |
23 |
user usages all the way through becoming a 'stong-user' and into the |
24 |
proxy-maint system. I think it is time to file a bug (documentation |
25 |
requests) @ bugs.gentoo.org formally requesting some documentation on |
26 |
git(hub) that is gentoo specific. |
27 |
|
28 |
That way everyone with questions, ideas and antedotes can 'pile on' and |
29 |
so the process get's started to document preferred/supported ways to use git |
30 |
with gentoo. There are lots of hints floating around so a FAQ or basic |
31 |
document is in order, imho. But, being so vocal on this topic, I'd really |
32 |
be encouraged if someone else opened up a formal (bug) request for some |
33 |
basic git documentation, that is gentoo centric. Posting the bug number |
34 |
back to this list could then encourage construction ideas and antedotes. |
35 |
|
36 |
|
37 |
hth, |
38 |
James |
39 |
|
40 |
|
41 |
|
42 |
|
43 |
> |
44 |
> Best regards |
45 |
> Marco |
46 |
> |
47 |
> On Thu, 16 Jun 2016 11:46:12 -0700 |
48 |
> Bryan Gardiner <bog <at> khumba.net> wrote: |
49 |
> |
50 |
> > On Thu, 16 Jun 2016 17:52:26 +0200 |
51 |
> > marco <at> nucleus.it wrote: |
52 |
> > |
53 |
> > > Hi, |
54 |
> > > i have a layman git profile to store my stuff. |
55 |
> > > |
56 |
> > > Is possible to force layman -S to sync a specific branch ? |
57 |
> > |
58 |
> > This is speculation (and a bit of looking at Portage code), since I |
59 |
> > haven't tried this. Ignoring Layman, repos.conf repositories support |
60 |
> > syncing[1], so does it work to create: |
61 |
> > |
62 |
> > /etc/portage/repos.conf/myrepo.conf: |
63 |
> > |
64 |
> > [myrepo] |
65 |
> > location = /path/to/local/repo |
66 |
> > sync-type = git |
67 |
> > sync-uri = git://... |
68 |
> > auto-sync = yes |
69 |
> > |
70 |
> > and just emerge --sync? If you didn't have the local repo already |
71 |
> > then it would clone and use master, but I suspect that you can switch |
72 |
> > branches afterward, and Portage will simply call "git pull". |
73 |
> > |
74 |
> > There also seem to be extra options "sync-git-clone-extra-opts" and |
75 |
> > "sync-git-pull-extra-opts" for git modules, so you might be able to |
76 |
> > set: |
77 |
> > |
78 |
> > sync-git-clone-extra-opts = --branch somebranch |
79 |
> > |
80 |
> > to fix initially checking out master. |
81 |
> > |
82 |
> > HTH, |
83 |
> > Bryan |
84 |
> > |
85 |
> > [1] https://wiki.gentoo.org/wiki/Project:Portage/Sync |
86 |
> > |
87 |
> |
88 |
> |