1 |
I don't buy any of that, release the code a prove what you say is true. We |
2 |
all know releng uses catalyst to master there iso's. Why wouldn't you in |
3 |
this case? what is the point of Catalyst but to create the Gentoo's master |
4 |
iso's? |
5 |
|
6 |
And where is this elusive cvs for Catalyst 2? |
7 |
|
8 |
I'm really glad your upstream providers dont treat you guys this way. |
9 |
Imagine bash with out make files... I can just hear GNU saying "make your |
10 |
own make files" ... google it. |
11 |
|
12 |
And no I'm not troll since I can be reasoned with, my request is reasonable. |
13 |
I havent seen any movement on your behalf Chris to even remotely trying to |
14 |
help me. |
15 |
|
16 |
On 10/20/05, Chris Gianelloni <wolf31o2@g.o> wrote: |
17 |
> |
18 |
> On Thu, 2005-10-20 at 16:16 -0400, Michael Crute wrote: |
19 |
> > On 10/20/05, Mike Rosset <schizoid29@×××××.com> wrote: |
20 |
> > I've all ready asked for those and got shot down appartently |
21 |
> > Chris wont release them. Also Chris will try to bump this to |
22 |
> > another list releng, more then likely |
23 |
> > |
24 |
> > Why not release them? Is this not open source? What's so secret about |
25 |
> > an iso image? |
26 |
> |
27 |
> Ehh... I'm not releasing it because it won't work for you. It's really |
28 |
> that simple. When I was working on the ISO, rather than doing things |
29 |
> "right" and extensible, I did them "quick and dirty". I added |
30 |
> hard-coded paths. I changed pieces of code that I know will break other |
31 |
> things. Besides this, I *still* have to do manual intervention in some |
32 |
> places to get things to work. |
33 |
> |
34 |
> Basically, if I took a dump in a bag and gave it to you, you'd get about |
35 |
> as much use out of it. If you want to look at my turd, at least let me |
36 |
> polish it for you. |
37 |
> |
38 |
> Also, there's nothing "open source" about the spec files used to build a |
39 |
> CD. While catalyst is released under the GPL, and the individual |
40 |
> packages are released under some open source license or another, the |
41 |
> actual spec files aren't under any license until I release them. The |
42 |
> *only* reason that they get released is because of the general open |
43 |
> nature of Gentoo, not because of any licensing requirement. Basically, |
44 |
> they get released because I want to release them. At any rate, as I've |
45 |
> stated a few times (thanks for the troll, Mike!) already, I'll release |
46 |
> proper spec files after the release of catalyst 2.0, once there is |
47 |
> actually something that makes the spec files usable. Until that time, |
48 |
> you can consider the spec files under the FWO (For Wolf Only) license. |
49 |
> If you want to peek at them, I'll fax you a NDA for you to sign after |
50 |
> you send me the check for a FWO license... :P |
51 |
> |
52 |
> I could release what I have right now, but you wouldn't understand how |
53 |
> it works, since they would not work with any released version of |
54 |
> catalyst. They wouldn't even work with catalyst 2.0 from CVS. My spec |
55 |
> files work *only* on my *one* workstation that I've been using to build |
56 |
> the LiveCD on, simply because I was lazy and under a lot of pressure to |
57 |
> produce the CD in a very limited amount of time and have no interest to |
58 |
> spend countless hours cleaning it up just so I can release it in its |
59 |
> current ugly state. Most of the code has already been pushed into |
60 |
> catalyst 2.0 CVS, but there's still a few patches I have to add before |
61 |
> that goes out for release. |
62 |
> |
63 |
> -- |
64 |
> Chris Gianelloni |
65 |
> Release Engineering - Strategic Lead |
66 |
> x86 Architecture Team |
67 |
> Games - Developer |
68 |
> Gentoo Linux |
69 |
> |
70 |
> |
71 |
> -----BEGIN PGP SIGNATURE----- |
72 |
> Version: GnuPG v1.4.2 (GNU/Linux) |
73 |
> |
74 |
> iD8DBQBDV//FkT4lNIS36YERAkIwAJ98BqzhJCluuQrn+Hvx/0t2JH+48gCfW4Nn |
75 |
> YZ17k4QijCTpHjKJMXw2BGs= |
76 |
> =4lUk |
77 |
> -----END PGP SIGNATURE----- |
78 |
> |
79 |
> |
80 |
> |