#457 closed defect (wontfix)
Instead of using ../package-build dir, use an obj dir of some sorts in the main dir (ie: glibc-2.3.1/obj) to build in.
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | lowest | Milestone: | |
| Component: | Book | Version: | CVS |
| Severity: | normal | Keywords: | |
| Cc: |
Description
This saves needing to hard-code the version number in the command installation instructions.
Change History (3)
comment:1 by , 21 years ago
comment:2 by , 21 years ago
| Priority: | high → normal |
|---|
comment:3 by , 21 years ago
| Priority: | normal → lowest |
|---|---|
| Resolution: | → wontfix |
| Status: | new → closed |
Points noted. Wildcards have their appeal but I feel they are not apprpriate for the book. Also ack' your point build-<package name> but the book's commands are not about making your scripts easier to write :-) I'll prefer to keep the current names. Thanks anyway.
Note:
See TracTickets
for help on using tickets.
I think I started this discussion and after have done so I actually came across a problem in glibc or gcc that was caused by this (first time this happend). so after thinking about some of the other comments made on that thread I think the best soluton was to use a directory called build-<package name> rather than <package name>-build.
this solves the problem of using the version number in the build command in my own scripts ie. it becomes possible to use ../glibc*/configure since ../glibc-build no longer is present. Unfortunately using a wildcard in a command might not be desirable for use in the book.
That being said I still like build-<package name> <package name>-build since