On Friday, March 14, 2003, at 12:01 PM, David R. Morrison wrote:
with it), but FinkCommander is the advice to go with at this point.
FinkCommander will be included on the next dmg.. don't forget to get me
to do that when you start making the bindist.
-Ben
---
Martin Costabel <[EMAIL PROTECTED]> wrote:
[snip]
> Then there is dselect which is still recommended on the download page. I
> think no innocent newbie should be asked to use dselect, the shock might
> be too strong. Actually I wonder how many potential Fink users give up
> at this point to be
How about this to go after the existing section 3 in the Quick Start:
After doing this, check whether you have a file called .tcshrc in your
home directory using
ls -a ~/.tcshrc
If you do, then you'll want to open it using "pico .tcshrc". Add the
following line to it:
source ~/.cshrc
an
Martin Costabel <[EMAIL PROTECTED]> wrote:
[snip]
>
> What I tried was to install Fink from the binary installer and then
> texmacs from the bindist. This turned out to be impossible.
>
> The problem in this case is tetex-texmf whose bindist version is
> classified restrictive and therefore do
On vendredi, mars 14, 2003, at 16:34 Europe/Paris, Alexander Hansen
wrote:
On Fri, 2003-03-14 at 02:53, Martin Costabel wrote:
[]
existing ~/.tcshrc. On the Fink download page, this is still not
fixed.
This has been mentioned to me by various other users. I've been
meaning
to add a section to
On Fri, 2003-03-14 at 02:53, Martin Costabel wrote:
> The author of TeXmacs had less problems than me, because on the machine
> where he tried this procedure, Gerben Wierda's tetex was installed, so
> he could use the system-tetex package and managed to use the bindist for
> texmacs, after all.
Max Horn wrote:
[]
So I think it would be good to at least have a FAQ entry that explains
the reasons for this (legal issues), and how to work around it
(installing the missing package(s) from source).
There is one aspect of this situation that I haven't seen addressed yet:
Fink needs to make an
I'd say to make the URL be
http://fink.sourceforge.net/doc/users-guide/packages.php#bin-exceptions
That seques right into how to install from source.
On Thu, 13 Mar 2003, Ben Hines wrote:
>
> On Thursday, March 13, 2003, at 07:29 PM, Alexander Hansen wrote:
>
> > I put an entire section in th
On Thursday, March 13, 2003, at 07:29 PM, Alexander Hansen wrote:
I put an entire section in the Users Guide pages to this effect
already.
Maybe i'll just link to that in the FAQ.
FinkCommander displays the .info and .patch files now if you
double-click
on a package, so one can easily see the
I put an entire section in the Users Guide pages to this effect already.
Maybe i'll just link to that in the FAQ.
FinkCommander displays the .info and .patch files now if you double-click
on a package, so one can easily see the licensing. It might be worth
suggesting a License column.
On Fri, 14
On Thursday, March 13, 2003, at 04:34 PM, Max Horn wrote:
We keep getting requests / bug reports due to problems caused by
packages missing from the bindist (ghostscript). There is no really
useful error message printed in these cases by apt-get / FinkCommander
etc. right now...
We could add
We keep getting requests / bug reports due to problems caused by
packages missing from the bindist (ghostscript). There is no really
useful error message printed in these cases by apt-get / FinkCommander
etc. right now...
So I think it would be good to at least have a FAQ entry that explains
t
12 matches
Mail list logo
