Bug 244828 - Include kdesrc-build config hint with each branch to set tags correctly
Summary: Include kdesrc-build config hint with each branch to set tags correctly
Status: RESOLVED WORKSFORME
Alias: None
Product: kdesrc-build
Classification: Developer tools
Component: general (show other bugs)
Version: Git
Platform: Unlisted Binaries Linux
: NOR wishlist
Target Milestone: ---
Assignee: Michael Pyne
URL:
Keywords: investigated, triaged
: 245370 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-07-16 09:23 UTC by Aaron Peterson
Modified: 2018-10-21 04:42 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Peterson 2010-07-16 09:23:22 UTC
Version:           Subversion (using KDE 4.4.4) 
OS:                Linux

Apparently KDESupport and others need specific settings to be set when a branch is selected.  Also appears that config for TRUNK needs tweaking because it doesn't work out of the box.

We could have a file called kdesrc-build_hint included, added to each older branch too, that includes version specific fixes to the script to allow it to build.

Reproducible: Always

Steps to Reproduce:
Try kdesrc-build, 
get stuck on qt-copy, phonon, kdelibs
read error messages, try -v, error messages offer no more details
set to a branch and use system-qt
get further
search internet for hours
find somebody on IRC that gives a fix regarding a tag setting that wasn't anywhere else on the net, and formatted differently than in the instructions
get something that sort of works, but .xsession fixing instructions are out of date

Actual Results:  
Tried using kdesrc-build as different users, with different settings.


There could also be "hints" for distros, or other conditions.
Comment 1 Michael Pyne 2010-07-20 04:09:55 UTC
I realize that it's kind of hard to document things after the fact (especially after aggravating debugging sessions) but this is very vague.

* What tag settings were missing or not documented?
* What error messages were listed when kdesupport, kdelibs, or qt-copy didn't compile?
* What distro-specific problems did you have?
* What .xsession instructions are you referring to? (e.g. a URL would suffice)

I'm perfectly willing to document things (probably in the kdesrc-buildrc-sample instead of a separate one) but I need to know what's wrong.
Comment 2 Aaron Peterson 2010-07-22 00:59:50 UTC
*** Bug 245370 has been marked as a duplicate of this bug. ***
Comment 3 Aaron Peterson 2010-07-22 01:21:05 UTC
Please forgive me as I am in a state of confusion.
I believe that what I am asking for is more sample rc files, one that builds each version of the branch... with options already ready to go.

Basically collect buildrc files from people who have it working, and name them 

buildrc_kubuntu10.04_trunk, etc.

kdesrc-build is bigger than I thought it was, and there are so many possible targets..

Here are some documentation issues with tag:
module-base-path tags/kdesupport-for-4.5
is syntax that works, that somebody gave me on IRC,
but in the buildrc-sample it reads:
tag kdesupport-for-4.4/kdesupport

so I uncommented it, and substituted 4.5 for 4.4 and it did not work at all.
With syntax from IRC, it fails to install.


The .xsession instructions I attempted to follow are at:
http://kdesrc-build.kde.org/documentation/environment.html
I will have to try again


Basically, Once I get it set up and working, I will share my kdebuildrc, and am basically begging for somebody elses working copy, and think that it would be really awesome if they were also included with kdesrcbuild.
Comment 4 Aaron Peterson 2010-07-22 02:32:49 UTC
oh, of note, for the user where i am trying to install trunk, i did not have a kdesrc-buildrc 

I assumed that default would be ok.  
I then created one, and turned on phonon in qt- and commented out the other phonon module and it appears to be doing more than before.

This was hinted about in the kdesrc-buildrc documentation, 

A colorization of the note that I did not have config file set up might help idiots like me notice it better. line 2823


Also, Do default values==sample buildrc file?
if not,
perhaps having a default-kdesrc-buildrc file that gets used instead of hard coded values could help people adapt their buildrc.
Comment 5 Andrew Crouthamel 2018-09-20 21:54:26 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-10-21 04:42:42 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!