| Summary: | Build issue: migratekde3 and r14-xdg-update scripts are install independently to any build rule. | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Alexander Golubev (Fat-Zer) <fatzer2> |
| Component: | tdebase | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED FIXED | ||
| Severity: | trivial | CC: | bugwatch, darrella, fatzer2, slavek.banko |
| Priority: | P3 | ||
| Version: | R14.0.0 [Trinity] | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Bug Depends on: | |||
| Bug Blocks: | 1300 | ||
| Attachments: | tdebase-fix-migratekde3-install.patch | ||
What kind of problems? Out of curiosity, what systems are built without installing the starttde script? The migratekde3 script is not run automatically from anywhere. The script is intended solely as an administrative tool. Even if not using starttde, the r14-xdg-update script still needs to be run at least once when updating a profile from 3.5.x to R14. If these scripts are installed only on the condition that the packager is building starttde, then the scripts will not be available. Without running the r14-xdg-update script, profiles WILL exhibit problems. More information will help us. :) (In reply to comment #1) > What kind of problems? > Here is the problem with the cmake build scripts only... not with what the script is doing or should do... Each file should be installed with make install only if we pass the corresponding -DBUILD_* flag was passed to cmake. But this scripts are installed inconditionaly...I'm just quite nazi about this... The same problem was with the tsak krootbacking etc. last time I attempt to build trinity (see the commit 40bd0569). > Out of curiosity, what systems are built without installing the starttde > script? > I'm writing the ebuilds(compile/installation scripts) for gentoo. I've already tried it about a year ago but I've given up after the migration to git and renaming packages... > The migratekde3 script is not run automatically from anywhere. The script is > intended solely as an administrative tool. > > Even if not using starttde, the r14-xdg-update script still needs to be run at > least once when updating a profile from 3.5.x to R14. > > If these scripts are installed only on the condition that the packager is > building starttde, then the scripts will not be available. Without running the > r14-xdg-update script, profiles WILL exhibit problems. > If it should be ran only once, I see only two good times to do it: make a conditional run with starttde after the upgrade or run for each user after distribution-specific package is installed eg. starttde. > More information will help us. :) Okay. This is something Tim or Slavek will have to decide. I'm updating the summary to "Build issue:" because that is what we have configured in our search links. :) Fixed in GIT hash 0f891721. |
Created attachment 921 [details] tdebase-fix-migratekde3-install.patch subj. This leads to file collisions while packaging/installing. IMHO a good decision is to install them with kstart... or even add special flags for them or move them somewhere from the root...