[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #49330] Stale files after make install
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #49330] Stale files after make install |
Date: |
Thu, 13 Oct 2016 17:25:19 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 |
Update of bug #49330 (project octave):
Status: None => Wont Fix
_______________________________________________________
Follow-up Comment #1:
There is no solution for this. If you are following the development branch and
continually installing from development releases, the only way to make that
work is to delete the previous install yourself.
If a new m-file is created some time during the development of 4.3.0, and then
later deleted because it was a mistake, then yes that stale file will sit in
the install directory if you don't delete it yourself. This is the way every
autotools based project works and I don't think Octave should do anything
above and beyond what every other project out there does.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?49330>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/