Version: (using KDE KDE 3.1.2) Installed from: Compiled From Sources OS: I Don't Know The gideon project packaging and publishing dialog is promising, but it has some really really annoying inconsistencies : * In the tab "Source distribution" the name of the future tarball created should be indicated - there is enough space to add a label messing with %v %n does not give the will of messing with it. * There should be ONE place and ONE file for configuring the project version. It is not clearly indicated and thus very confusing. By the way, changing the version number everywhere in gideon still produces a tarball with an old version number. For now i find more easy to stick to this : grep the files to look for the version number, change them in every file with vim and then use "make dist" to generate the tarball. * When the tarball is created, indicate it in the statusbar of the dialog .. "Tarball XXXXXX created" * The dialog name doesn't match exactly the name in the menu (project distribution & packaging) * The icon should be the same as the nice icon (the big pixels ..) in the menu * The "ok/cancel" buttons should be replaced by one button "Done". There is no cancel mode. * The file list does not make the difference between files and directories included. The directories should perhaps be represented as [+] elements that can be opened ? Or with a particular color ? (just an idea)
In order to generate a rpm, the help says 'Generate a SPEC file'. It does not say how to generate this spec file, it does not say if gideon/kdevelop can generate it, and it does not tell what is this spec file is for.
In order to generate a rpm, the help says 'Generate a SPEC file'. It does not say how to generate this spec file, it does not say if gideon/kdevelop can generate it, and it does not tell what is this spec file for.
after creating the tarball; xseg-0.2.1.tar.gz in the package information tab, when i select src packages, src/binary packages; *cd /home/raist/xseg && cp xseg-0.2.1.tar.gz *cp: missing destination file *Try `cp --help' for more information. **** Exited with status: 1 does it try passing cp only one argument??
Also: 1. There is no possibility to make tarball or rpm of the build result of any of the default or other build configurations - that is only the files to be installed. Only distribution or source tarball can be made currently or I am missing something ? 2. You can work with the Distribution & Publishing manager only if the (Default) build configuration is configured, which is annoying when the other build configurations are configured and used. In such case the default shoul be not - autotools restriction.