By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1280 - Build issue: migratekde3 and r14-xdg-update scripts are install independently to any build rule.
Summary: Build issue: migratekde3 and r14-xdg-update scripts are install independently...
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: All Linux
: P3 trivial
Assignee: Timothy Pearson
URL:
Depends on:
Blocks: 1300
  Show dependency treegraph
 
Reported: 2012-10-20 08:29 CDT by Alexander Golubev (Fat-Zer)
Modified: 2012-12-13 19:22 CST (History)
4 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:


Attachments
tdebase-fix-migratekde3-install.patch (462 bytes, application/octet-stream)
2012-10-20 08:29 CDT, Alexander Golubev (Fat-Zer)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Golubev (Fat-Zer) 2012-10-20 08:29:26 CDT
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...
Comment 1 Darrell 2012-10-20 08:56:21 CDT
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. :)
Comment 2 Alexander Golubev (Fat-Zer) 2012-10-20 17:23:34 CDT
(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. :)
Comment 3 Darrell 2012-10-20 19:29:48 CDT
Okay. This is something Tim or Slavek will have to decide.
Comment 4 Darrell 2012-10-31 14:03:26 CDT
I'm updating the summary to "Build issue:" because that is what we have configured in our search links. :)
Comment 5 Slávek Banko 2012-12-13 19:22:04 CST
Fixed in GIT hash 0f891721.