#635 closed enhancement (wontfix)
Different ways of logging installed files
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | lowest | Milestone: | |
Component: | DTD | Version: | SVN |
Severity: | minor | Keywords: | |
Cc: |
Description (last modified by ) ¶
Check out install-log (http://install-log.sourceforge.net/) for example and what it can do, that we can't.
Change History (6)
comment:1 by , 22 years ago
qa_contact: | alfs-discuss@linuxfromscratch.org → alfs-log@linuxfromscratch.org |
---|
comment:2 by , 22 years ago
Owner: | changed from | to
---|---|
Version: | CVS → 1.1.7 |
comment:3 by , 22 years ago
comment:4 by , 20 years ago
Component: | Back End (XML Handlers) → DTD |
---|---|
dependson: | → 933 |
Milestone: | → nALFS2 |
Version: | 1.1.7 → SVN |
comment:5 by , 12 years ago
Description: | modified (diff) |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
{n,}ALFS is not developped anymore
Note:
See TracTickets
for help on using tickets.
install-log is indeed a nice program. However, for use with nALFS we may want to build something in. If nothing else, just to cut out a dependency and make it easier to run nALFS on different machines without having the need to install a third-party program. Maybe make it an optional thing to use if present, but if missing nALFS should default to a built-in way of doing something similar.