1 |
Hello Brian! |
2 |
|
3 |
Thanks for the fast answer! |
4 |
The biggest problem is that I've used only Kubuntu (for one year) and since |
5 |
that time I've been using openSUSE (for more than two years already). Is it |
6 |
hard for novice to use Gentoo if I know only basics of C and C++ and prefer |
7 |
to set up system using GUI rather than shell if it is possible (though |
8 |
sometimes I've had to change some things using shell before)? |
9 |
|
10 |
P.S. Will it be enough to setup Gentoo as virtual system like VirtualBox? |
11 |
Or it is better to free partition? |
12 |
|
13 |
|
14 |
2013/4/21 Brian Dolbec <dolsen@g.o> |
15 |
|
16 |
> On Sun, 2013-04-21 at 05:08 +0400, Dmitry Selyutin wrote: |
17 |
> > Hello everyone! |
18 |
> > |
19 |
> > |
20 |
> > My name is Dmitry and I'm writing here because I've found a proposal |
21 |
> > to rewrite Catalyst in Gentoo GSoC-2013 Ideas page[1]. I know that |
22 |
> > application period hasn't started yet, but I already think that I'd |
23 |
> > like to take up this job. However I've found that before posting |
24 |
> > application I must perform some actions: |
25 |
> > |
26 |
> > |
27 |
> > 1. Use the tools that you will use in your project to make changes to |
28 |
> > code. |
29 |
> |
30 |
> This is the big one. To be able to work on catalyst, you first must be |
31 |
> running and using gentoo linux and be familiar with it. Gentoo's |
32 |
> package management tools are central to running and using catalyst to |
33 |
> build various output media. If you are not already using gentoo, you |
34 |
> best get a partition free and install it asap. Become familiar with it. |
35 |
> |
36 |
> tools to be familiar with: |
37 |
> |
38 |
> portage and it's cli tools, emerge, emaint, portageq |
39 |
> gentoolkit's equery, eclean |
40 |
> |
41 |
> You must be familiar with using the above tools and solving build |
42 |
> problems and package installation failures. |
43 |
> |
44 |
> Then start trying to use catalyst to generate some targets. |
45 |
> |
46 |
> This is all information that will need for you to succeed in your |
47 |
> project proposal. |
48 |
> |
49 |
> |
50 |
> > 2. Participate in our development community. |
51 |
> > 3. Give us your contact info and working hours. |
52 |
> > |
53 |
> |
54 |
> [snip]... |
55 |
> |
56 |
> > The other question is that it is really hard to find some project |
57 |
> > which uses python and emit patch to it to pass requirements. Could you |
58 |
> > advice a good bug, please? :-) |
59 |
> > |
60 |
> > |
61 |
> Don't worry about that yet. It is early :) |
62 |
> |
63 |
> > If you think I have a chance, I can even answer the third question |
64 |
> > (about work hours, contacts, etc.). :-) |
65 |
> > |
66 |
> > |
67 |
> > Looking forward to your answers! |
68 |
> > |
69 |
> |
70 |
> This will be something for your actual proposal. It can be done later. |
71 |
> |
72 |
> > |
73 |
> > P.S. Thanks for being so patience to read such a long letter till the |
74 |
> > end! |
75 |
> > |
76 |
> |
77 |
> > -- |
78 |
> > With best regards, |
79 |
> > Dmitry Selyutin |
80 |
> > |
81 |
> > E-mail: ghostmansd@×××××.com |
82 |
> > Phone: +7(985)334-07-70 |
83 |
> |
84 |
> |
85 |
> |
86 |
> |
87 |
|
88 |
|
89 |
-- |
90 |
With best regards, |
91 |
Dmitry Selyutin |
92 |
|
93 |
E-mail: ghostmansd@×××××.com |
94 |
Phone: +7(985)334-07-70 |