1 |
Natanael Copa wrote: |
2 |
|
3 |
> On Mon, 2007-10-08 at 20:25 +0100, Steve Long wrote: |
4 |
>> Natanael Copa wrote: |
5 |
> |
6 |
>> If you're that motivated why not just start hacking on binary support in |
7 |
>> portage/pkgcore/paludis? There's always open bugs. |
8 |
> |
9 |
> I think I did contribute with some patches for qmerge in portage-utils. |
10 |
> |
11 |
Nice one! I really like portage-utils, they're good and fast. |
12 |
|
13 |
> Unfortunally, its pretty difficult to make a lightweight C (language) |
14 |
> only binary installer without having at least the eclasses and GNU |
15 |
> tools. |
16 |
> |
17 |
> It kind of defeat the idea of having a lightweight binary only runtime |
18 |
> environment. (lightweight means busybox - which give you most of the |
19 |
> basic GNU tools, linux-utils, wget, shell, http server and much more for |
20 |
> the size of bash only) |
21 |
> |
22 |
Yes but build time is not the same as runtime, especially for embedded |
23 |
systems. Installation doesn't have to be run by the target, which typically |
24 |
uses an image. |
25 |
|
26 |
>> I'd just specify BASH (as I don't see the point in making the distinction |
27 |
>> as it only applies to build machines) and coreutils/findutils etc. |
28 |
> |
29 |
> To properly install a prebuilt binary packages you need the pkg_* funcs |
30 |
> in the ebuild. |
31 |
> |
32 |
>> Asking everyone to switch coding style for certain functions, just to |
33 |
>> support the stuff that Gentoo was designed to do from the beginning, |
34 |
>> seems counter-productive. |
35 |
> |
36 |
> We already do different for init.d scripts (which is great!) , but sure, |
37 |
> I get the point. |
38 |
> |
39 |
That's entirely proper and reasonable to me, since it means the installed |
40 |
system can use whatever shell it likes. |
41 |
|
42 |
>> For every market except embedded, which we've discussed |
43 |
>> already, BASH is not a major issue: nor are the other tools mentioned. |
44 |
> |
45 |
> I happen to do embedded. |
46 |
> |
47 |
I don't understand then why you cannot build images using whatever tools you |
48 |
like and then simply run them using the targets. Apologies if I am missing |
49 |
something. |
50 |
|
51 |
>> > |
52 |
>> > Alternative C is what I do today. |
53 |
>> > |
54 |
>> Sounds rough :) |
55 |
> |
56 |
> Thats why I'm interested in alternatives. |
57 |
> |
58 |
>> (I really would recommend #pkgcore as well as there is several years of |
59 |
>> work to do with binpkgs in that.) |
60 |
> |
61 |
> So far no packagemanager using the portage stuff (eclasses) are not even |
62 |
> close to compete in size for binary only installs. Closest is |
63 |
> portage-utils's qmerge but it would need atleast the eclasses and bash |
64 |
> which would atleast double the size in comparison what I do today. |
65 |
> |
66 |
> Looks like i will need to continue do my own stuff. |
67 |
> |
68 |
> Thanks for you time! |
69 |
> |
70 |
Good luck with it! I recommend #gentoo-embedded on irc.freenode.org btw; |
71 |
##electronics is good. Some of the bods in #gentoo-chat have experience |
72 |
with this kinda thing as well, and you'd be welcome in #friendly-coders. |
73 |
|
74 |
|
75 |
-- |
76 |
gentoo-dev@g.o mailing list |