RPM builds under Kdevelop 2.0.2

[W. Tasin]

Hi,

there was a little bug inside am_edit (concerning the "make dist" 
functionality), so it doesn't work.

First at all, IMHO the admin-dir and Makefile.dist shouldn't be a part 
of the distribution-tarball.

But for solving your problem you can either use the next kdevelop 
version ;-) and create a new project with it (adding then your sources, 
etc. etc.)

or you can patch your toplevel Makefile.am and add "subdirs" to the 
EXTRA_DIST= variable.

After that it should be possible to make a distribution-tarball.

If you want adding the admin/ directory to your distribution-tarball 
then you will add "admin" and of course "Makefile.dist" (without 
Makefile.dist the admin/ would make no sense) to the EXTRA_DIST 
variable, too.

Take care: using "Update Makefile.am" or "Update all Makefile.ams" 
inside KDevelop would revert these changes.
Please remember: before recreating a new distribution-tarball, you 
should delete the old appname-0.1.tar.gz.

So these are the commands you would use outside KDevelop to make a 
tarball (and of course you could do the same from within KDevelop):
#cd appname
#rm appname-0.1.tar.gz
#make distclean
#make -f Makefile.dist
#./configure ........
#make dist


Then you have the tarball inside your toplevel-project directory.
After that you always should try out this tarball (building/installing) 
before creating a rpm-package (only to know that further errors would be 
caused by an error inside the spec file):

#cd ..
#tar xvzf appname/appname-0.1.tar.gz
#cd appname-0.1.tar.gz
#./configure ..........
#make
#su -c "make install"

check if all your files are installed and then uninstall your application.

#su -c "make uninstall"

Only to check later, if the rpm-package will work correctly.

That's all...

Ciao

Walter

Tim Brodie wrote:

>Steven Suson wrote:
>
>>Not a clue on this one.... Anyone else? Did you follow the steps beginning w/
>>Distclean?
>>
>>Tim Brodie wrote:
>>
>>>Right now, when I get to the making of the source tgz, there is an
>>>error: "Can't open perl script "admin/am_edit": No such file or
>>>directory"
>>>It appears as though the admin directory isn't picked up as the
>>>tool builds the appname-0.1 staging directory.  How best to fix
>>>that?
>>>
>
>Yes, I did.  I think that one of my project files was damaged when
>I was (like a big lout) turning on and off specific files to be
>included in the project.
>
>I've been trying to reverse engineer the make process, and which
>file(s) must have lost the reference to the admin directory.  It's
>pretty complicated, though and I'm not having much luck as yet.
>
>Any leads would be greatly appreciated.
>
>--
>Tim Brodie
>
-- 
The KDevelop project: tasin at kdevelop.de [www.kdevelop.org]
--
oohhh sveglia.... il mondo e' ammalato, ma x colpa di chi.........
(Zucchero)
:-------W. Tasin, FB 04,FHM-------------------PGP-KeyID:0x7961A645----------:
<Key-Fingerprint: 1610 835F 0080 32F4 6140  6CF7 A7D0 44CD 7961A645>




-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«