| Summary: | Build issue: Konversation Sym Links Incorrect | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Darrell <darrella> |
| Component: | other (any) | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | CC: | bugwatch, darrella, michele.calgaro, slavek.banko |
| Priority: | P1 | ||
| Version: | R14.0.0 [Trinity] | ||
| Hardware: | Other | ||
| OS: | All | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Bug Depends on: | |||
| Bug Blocks: | 2014 | ||
|
Description
Darrell
2011-11-16 00:42:36 CST
Hey, I am getting build errors with the cmake port. Is this fully working on your machine? R14 nightly wheezy here. Calvin Seems bug report 1365 is the appropriate place for your question. :) (In reply to comment #2) > Seems bug report 1365 is the appropriate place for your question. :) Don't know how I mixed that up... to many tabs open! Darrell, is this bug still valid? Read my previous replay: http://bugs.pearsoncomputing.net/show_bug.cgi?id=613#c2 While I understand Slavek's arguments, I don't believe the master package should automatically create empty or dangling sym links. When sym links are needed to the common directory then the subservient i18n package should create the sym link when installed. Here is a list of all such reports: http://bugs.pearsoncomputing.net/buglist.cgi?quicksearch=sym%20links&list_id=273 (In reply to Darrell from comment #5) >While I understand Slavek's arguments, I don't believe the master package >should automatically create empty or dangling sym links. I understand Slavek's arguments too, but I also think dangling sym links are not a good idea as you think. We will have to discuss all together to find a good solution for this kind of problem (I saw several bugs in this category, so once we fix once, we will be able to do the others as well). (In reply to Michele Calgaro from comment #6) I think we should address this type of bugs before releasing v14.0.0 (In reply to Darrell from comment #5) > Read my previous replay: > > http://bugs.pearsoncomputing.net/show_bug.cgi?id=613#c2 > > While I understand Slavek's arguments, I don't believe the master package > should automatically create empty or dangling sym links. When sym links are > needed to the common directory then the subservient i18n package should > create the sym link when installed. > > Here is a list of all such reports: > > http://bugs.pearsoncomputing.net/buglist. > cgi?quicksearch=sym%20links&list_id=273 It is nonsense to symlinks in the manuals applications were supplemented by packages tde-i18n-<lang>. When the package tde-i18n-<lang> will be installed before the applications, then symlinks will be missing. So package tde-i18n-<lang> would had to react after installing "each" other package - and this is simply nonsense. I dare say that dangling symlinks is now the only reasonable solution. The question is: Who can hit on dangling symlinks? What is the probability, for example, that one of you will open Czech guide for knutclient? I think that is very small. On the contrary, it is very likely that the person who will open this guide, will have already installed package tde-i18n-cs and symlinks for his language will be in order. Closed as WONTFIX. See comments in bug 1611 for details. |