Author Topic: making installation package  (Read 6180 times)

vyankatesh

  • Newbie
  • *
  • Posts: 2
making installation package
« on: April 17, 2007, 12:19:27 AM »
I am new to using linux and Gambas. I have Ubuntu 6.10 and Gambas 1.0.15. When I try to "make an installation package" of a program developed by me, it offers choice of only Mandriva, Debian, Redhat and Suse. What should i choose if i want to deploy the installation (program) on  another machine running either Ubuntu or Damn Small Linux?  Thanks in advance. regards.

Linux Basic

making installation package
« on: April 17, 2007, 12:19:27 AM »

timothy

  • Sr. Member
  • ****
  • Posts: 319
Re: making installation package
« Reply #1 on: April 17, 2007, 01:26:20 AM »

Mandriva, Redhat and Suse all use the rpm package management system. Ubuntu and Debian use the deb package management system. Also Ubuntu is built on Debian. So I guess Debian is most likely to work. I have not tried it. I have read that not all Debian  packages install on Ubuntu so you must test it.

Damn Small Linux is also built  on Debian packages. So the same applies here. Again you must test it.

42 - So long and thanks for all the fish.

vyankatesh

  • Newbie
  • *
  • Posts: 2
Re: making installation package
« Reply #2 on: April 17, 2007, 06:18:11 AM »
thanks for the prompt advise, timothy. I tried with the debian option, but i receive the following error message, " [-1] error: File /home/vyankatesh/RPM/SOURCES/SerialPort-&1.&20.0.tar.bz2: No such file or directory. Package.MakePackage.440". My program is simple; open serial port and transmit the character input by the user. It works fine when run through the Gambas environment and tested the working by connecting it to a PC running Hyper Terminal (on WIn XP). Do the files to be used for installation package need to be kept is any particular folder, I wonder? Thanks in advance. Regards.

flattery

  • Newbie
  • *
  • Posts: 16
Re: making installation package
« Reply #3 on: May 09, 2007, 05:03:09 PM »
I have had multiple problems making packages myself.

1st I couldn't get the debian package to make, but I could make the rest so I just manually did an alien on the redhat rpm and that made a .deb for me.

But now all of the sudden none of them work any more.

For example when I try to make the redhat package I get the error:
Unable to load image
Package.Makepackage.192

Nothing has changed on my sytem. The only thing I use this one for is gambas development, so I haven't use anything, but gambas... no update or anything...   worked earlier and now it doesn't.

flattery

  • Newbie
  • *
  • Posts: 16
Re: making installation package
« Reply #4 on: May 09, 2007, 05:20:04 PM »
Figured out my image loading issue.  I deleted the icon,but it still listed it in the .project file.

timothy

  • Sr. Member
  • ****
  • Posts: 319
Re: making installation package
« Reply #5 on: May 10, 2007, 01:42:25 AM »

The process for making a package has been rewritten and is being tested. So it might be better to wait until this is complete. Or even better download that latest svn version of Gambas and try it for your self. Just expect a few bugs and report them on the Gambas mailing list.

42 - So long and thanks for all the fish.

Mario

  • Newbie
  • *
  • Posts: 10
Re: making installation package
« Reply #6 on: July 17, 2007, 01:25:58 PM »
Found an issue myself. I tried to make a Debian package and everything seemed to work without errors. Gambas reported that the package has been built successfully but that wasn't the case. There wasn't any package.

I checked out the svn trunk and started gambas again for debugging purposes. While creating the package again I found out that dpkg-buildpackage stopped with an error ("Build dependencies/conflicts unsatisfied; aborting."). Unfortunately there's neither an option to show the output of dpkg-buildpackage in the status textbox nor an evaluation of the return code.

Package.module:
Code: [Select]
  368   AddLog(("Creating package..."))
  369   sCmd = "cd " & Quote.Shell(sPackagePath) & "; fakeroot dpkg-buildpackage > /dev/null"
  370   SHELL sCmd WAIT FOR READ

Where can I report this behaviour as a bug? Does a bugtracker exist for this project? I don't want to subscribe to any mailing list. I hate mailing lists.

timothy

  • Sr. Member
  • ****
  • Posts: 319
Re: making installation package
« Reply #7 on: July 21, 2007, 01:21:08 AM »

It is quite complex to build a utility that will create install packages for all distributions of Linux. The one in the latest version of Gambas (1.9.49) has just been rewritten.

How to report a bug? Sorry, but it is a mailing list >:( Go to https://lists.sourceforge.net/lists/listinfo/gambas-user and follow the instruction to create an account. Then you can post your bug report.

Its not such a bad mailing list. Give it a try ;D But if you really do have a phobia about such lists then post your bug report here and I shall send it in. Just remember to include:
  • The version of Gambas that contains the bug
  • The Linux distribution you are using
  • A description of how to create the bug
  • If necessary a code sample that illustrates the bug. If you do include a code sample strip it down to the minimum needed to illustrate the bug.

You can look at the items sent to the mailing list without subscribing. Just go to the link: http://www.nabble.com/Gambas-f3425.html
42 - So long and thanks for all the fish.

Mario

  • Newbie
  • *
  • Posts: 10
Re: making installation package
« Reply #8 on: July 21, 2007, 11:01:10 AM »
Thank you for your offer, timothy!
I don't like mailing lists because I can't decide what topics to receive. As you might imagine I get enough mail that I don't want to read. I really don't know why this lists exist anymore. This is 2006 and we've got bulletin boards (like this one here) and bugtrackers that are much better than getting tons of mails you don't want to receive. anyway...

If you don't mind, here's my report:
- Gambas version is the latest trunk (1.9.49)
- Distro is Kubuntu Feisty Fawn
- Description: Start making an installation package like you normally would do. Choose a Debian system. Finish the job. You get no error messages but no deb file has been created. There's no way to find out that dkpg-buildpackage reported an error behind the scenes.
- code sample (as written above)

Thank you in advance.

timothy

  • Sr. Member
  • ****
  • Posts: 319
42 - So long and thanks for all the fish.

Mario

  • Newbie
  • *
  • Posts: 10
Re: making installation package
« Reply #10 on: July 22, 2007, 06:16:16 AM »