Opened 18 years ago
Closed 17 years ago
#2234 closed task (fixed)
kdewebdev runtime dependencies
| Reported by: | Owned by: | Robert Daniels | |
|---|---|---|---|
| Priority: | normal | Milestone: | 6.3 |
| Component: | BOOK | Version: | SVN |
| Severity: | normal | Keywords: | |
| Cc: |
Description ¶
As soon as we figure out the way we are going to mention run time dependencies, we can add the following to kdewebdev for the quanta application:
tidy
gpg
kompare (from kdesdk)
cervisia http://kde.org/apps/cervisia (CVS front end)
Change History (5)
comment:1 by , 18 years ago
| Milestone: | 6.2.1 → 6.3 |
|---|
comment:2 by , 17 years ago
comment:3 by , 17 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:4 by , 17 years ago
I plan to revisit the dependencies for the rest of kde while working on this. For example htdig can be used for indexing the help system, and I think cvs is actually needed for kdesdk, not subversion.
I would also like to move the runtime dependencies that are already listed for kdelibs and kdebase up to just below the build dependencies, as I think that is more logical. Any objections?
Note:
See TracTickets
for help on using tickets.
My feeling is the run-time dependencies can be listed under the required or optional ones (usually just a paragraph with no header, but a header would be okay as well), or listed in the configuration section, whichever may be best for the package.
Some packages have no configuration, but do have run-time dependencies, so I suppose it's up to the Editor. I really don't have a preference as long as the run-time dependencies are annotated.