1 |
One general Question: |
2 |
How can open source packages work on Unices which are non-Gentoo-Linux |
3 |
if there are that many unresolved issues you try to point out ? |
4 |
|
5 |
This is what autoconf and libtool are for, and if a package lacks using |
6 |
them, autoconf/libtool-like trickery has to be done in ebuilds. |
7 |
|
8 |
There are always 'what if' situations, where the secondary package |
9 |
manager cannot be responsible for. Portage and ebuilds have to avoid |
10 |
_all_ those situations _only_ if portage is the _primary_ pkg mgr. |
11 |
|
12 |
As secondary pkg mgr, _some_ basic working things must be presumeable. |
13 |
|
14 |
Ciaran McCreesh wrote: |
15 |
> On Thu, 19 May 2005 13:05:20 +0200 Michael Haubenwallner |
16 |
> <michael.haubenwallner@×××××××.at> wrote: |
17 |
> | Most of the packages (not ebuilds) wont work on systems without |
18 |
> | /bin/sh (Bourne-Shell, not bash) and /usr/bin/env, so there's no need |
19 |
> | to have a Bourne-Shell installed in /my/prefix/bin/sh instead of |
20 |
> | /bin/sh. |
21 |
> |
22 |
> So what if /bin/sh is a nastily h0rked non-POSIX implementation? Or what |
23 |
> if we have packages with a dep upon a specific sh version? The portage |
24 |
> provided version must be used in all cases. |
25 |
|
26 |
If /bin/sh is a bad shell, many packages wouldn't work, |
27 |
independend if installed by hand or by portage/ebuilds. |
28 |
|
29 |
And if a package depends on specific version, it is able to find such a |
30 |
version itself or at least to specify the location of the right version. |
31 |
|
32 |
> | Once this is done, this line will find the portage-installed |
33 |
> | interpreters: |
34 |
> | #! /usr/bin/env {bash,perl,python,whatever} |
35 |
> |
36 |
> No good, because we won't be using the portage-provided env binary. And |
37 |
> that only works for things that actually use env (which is considered |
38 |
> discouraged). |
39 |
|
40 |
Same here, if a package cannot operate with /usr/bin/env on |
41 |
non-Gentoo-Linuxes, and is dedicated to run on such Unices, |
42 |
it should be able to find the right one or get it specified. |
43 |
|
44 |
No somewhat correct package, which says to run on Unix, should have |
45 |
hardcoded '#! /usr/bin/perl' but find it in PATH. |
46 |
|
47 |
> | autoconf-checks: i configure gcc '--with-local-prefix=/my/prefix' in |
48 |
> | case of prefix!=/usr, so gcc searches in |
49 |
> | "/my/prefix/lib:/usr/lib:/lib" for libraries by default, and the |
50 |
> | checks should rely on the compiler to find the right libraries when |
51 |
> | configuring. |
52 |
> |
53 |
> I could dig out a rather large list of annoying counterexamples, all of |
54 |
> which would need manual fixing... |
55 |
> |
56 |
|
57 |
Sure, but what's the problem with manual fixing ? |
58 |
The one who needs it will look for how to fix it. |
59 |
|
60 |
And why not let portage support features not required for Gentoo-Linux ? |
61 |
|
62 |
Portage is just another open source package, which is able to be ported |
63 |
to other Unices, with the power to become _the_ secondary pkg mgr. |
64 |
|
65 |
~haubi |
66 |
-- |
67 |
Michael Haubenwallner SALOMON Automation GmbH |
68 |
Forschung & Entwicklung A-8114 Friesach bei Graz |
69 |
mailto:michael.haubenwallner@×××××××.at http://www.salomon.at |
70 |
No HTML/MIME please, see http://expita.com/nomime.html |
71 |
-- |
72 |
gentoo-dev@g.o mailing list |