aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Why not to release a amule package for autopackageinstead of foucosing in each distro individualy?  (Read 3420 times)

psmmr

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 10
Why not to release a amule package for autopackageinstead of foucosing in each distro individualy?
« on: February 15, 2005, 11:16:37 PM »
http://autopackage.org/

I don't understand why do u ppl loose yr time writing packages for each linux distro. This thingie here works very well and it suits all the packages at once... I don't even get why don't the most software developers use this..
Logged

skolnick

  • Global Moderator
  • Hero Member
  • *****
  • Karma: 24
  • Offline Offline
  • Posts: 1188
  • CentOS 6 User
Re: Why not to release a amule package for autopackageinstead of foucosing in each distro individualy?
« Reply #1 on: February 16, 2005, 02:38:49 AM »
does it take into account the different library versions available in the different distros? and the required ones by the software?

Regards.
Logged

Xaignar

  • Admin and Code Junky
  • Hero Member
  • *****
  • Karma: 19
  • Offline Offline
  • Posts: 1103
Re: Why not to release a amule package for autopackageinstead of foucosing in each distro individualy?
« Reply #2 on: February 16, 2005, 02:58:42 PM »
I'm not sure that it is feasible for aMule:
Quote
# Can I autopackage KDE/Qt apps?

Generally no, because the C++ ABI is not stable. It was supposd to be, but then gcc 3.4 broke it yet again. Until we have a stable C++ ABI on Linux distributing binaries that link against anything other than the standard library is a bad idea. GTKmm apps are OK because you can statically link GTKmm and not suffer too badly, but Qt/KDE cannot be statically linked in a sensible fashion.

The solution of course would be to make wx static, but I dont know how much that increases the size of the binary, so that has be examined before this can be considered.
Logged

Vollstrecker

  • Administrator
  • Hero Member
  • *****
  • Karma: 67
  • Offline Offline
  • Posts: 1550
  • Unofficial Debian Packager
    • http://vollstreckernet.de
Re: Why not to release a amule package for autopackageinstead of foucosing in each distro individualy?
« Reply #3 on: February 16, 2005, 08:10:09 PM »
From their IRC:
Hi. Can autopackage build debs conform to debian policy?
no.

I would miss features like pre/post-install/remove scripts and so on.
Logged
Homefucking is killing prostitution

lfroen

  • Guest
Re: Why not to release a amule package for autopackageinstead of foucosing in each distro individualy?
« Reply #4 on: February 17, 2005, 09:43:25 AM »
I would summarize my experience with this in 2 words "does not work". ok, it's 3 words. All the clutter about "can't do such and such".
If still unsure - take a look to autopackage FAQ section "I bet autopackage sucks because ...". Yes, you right, it sucks. And plenty of reasons why.

The main line is following: you can't mix more then 1 install-managing systems in single computer without having "fun" of manual conflict and/or dependancy resolving.
Every time I see something like this I'm thinking - WTF does those folks think ?! What is this magical thingie that convince them that their package system XYZ is better then 3 already existing (RPM, debian, gentoo) and others that I'm not aware of ?
"Distribution neutral" ?! What's a weird idea ! Who says that RPM is not ? Go ahead, compile rpm (or apt-* or ebuild) on your platform and I bet that you will have same effect.
Logged