Active Topics
-
Porting apps to Leste (32)
to Maemo 7 / Leste by Arno_11 - 2 days, 9 hrs ago -
[ANNOUNCE] CSSU-thumb thread - stable Thumb2 on N900 (2,264)
to Maemo 5 / Fremantle by panjgoori - 4 days, 3 hrs ago -
Full linux distros on Sailfish OS (254)
to SailfishOS by qoh - 5 days, 1 hr ago - more...
| The Following User Says Thank You to egoshin For This Useful Post: | ||
|
2010-02-19
, 20:03
|
|
Posts: 3,428 |
Thanked: 2,856 times |
Joined on Jul 2008
|
#182
|
Originally Posted by egoshin
If a certain package required changes to compile on ARM/ARMEL and debian has already done that for us.. we can simply take the debian deb and repackage the binaries.. or grab the sources from debian with the changes.
Exactly!
Actually - NO. If you want to port, there is no difference where you get the sources. In most cases you get it's last version from sourceforge or application web site and that would be in .tar file.
The only exclusion - if you port a system maintenance application which works in the same model as your debian-based system AND your window manager. So, Gnome vs KDE plays role but DEB vs RPM - not.
I remember having to modify a few things to get KDE4 to compile right for debian on the N810... this was before debian had ARM ports in their repo's for it.
So.. having a major distribution supporting your architecture certainly does help with porting... however - there's no reason one can't use the debian sources in this case and build an RPM instead.
|
|
2010-02-19
, 20:09
|
|
Posts: 992 |
Thanked: 995 times |
Joined on Dec 2009
@ California
|
#183
|
Originally Posted by fatalsaint
There is a chance that changes for ARM/ARMEL do exist in RPM source repositories too. Usually the package maintainers supports ALL platforms and if somebody needs yet-another platform then they include that fixes as well and with thanks to proposed changes. I never seen the situation then changes to some platform doesn't go it's way to original source... besides the very platform-specific applications, of course.
If a certain package required changes to compile on ARM/ARMEL and debian has already done that for us.. we can simply take the debian deb and repackage the binaries.. or grab the sources from debian with the changes.
| The Following User Says Thank You to egoshin For This Useful Post: | ||
|
|
2010-02-19
, 20:13
|
|
Posts: 3,428 |
Thanked: 2,856 times |
Joined on Jul 2008
|
#184
|
Originally Posted by egoshin
Except that the ARMEL repositories of RPM distributions are so utterly pathetic when compared to debians.
There is a chance that changes for ARM/ARMEL do exist in RPM source repositories too. Usually the package maintainers supports ALL platforms and if somebody needs yet-another platform then they include that fixes as well and with thanks to proposed changes. I never seen the situation then changes to some platform doesn't go it's way to original source... besides the very platform-specific applications, of course.
That's the debate. Why would RPM sources have the change when their distro doesn't cross-compile or maintain an active ARM repo? That would be pointless.
Anyway.. it's all moot: As long as there already is an ARM port of it somewhere.. it's stupid simple to make either a deb or rpm from it to fit our needs.
|
|
2010-02-19
, 20:23
|
|
Posts: 27 |
Thanked: 7 times |
Joined on Nov 2009
@ Lanzarote, Canary Islands
|
#185
|
Hi,
Has any one actualy used Moblin.
I am at present and its not Fedora. Mine
is Open suse Moblin although still using rpm's
KDE and Debian programs seem to be
available
Has any one actualy used Moblin.
I am at present and its not Fedora. Mine
is Open suse Moblin although still using rpm's
KDE and Debian programs seem to be
available
|
|
2010-02-19
, 20:27
|
|
Posts: 3,428 |
Thanked: 2,856 times |
Joined on Jul 2008
|
#186
|
Originally Posted by rushman
1) Yes
Hi,
Has any one actualy used Moblin.
I am at present and its not Fedora. Mine
is Open suse Moblin although still using rpm's
KDE and Debian programs seem to be
available
2) That's because there isn't really "debian" programs so much as debian has packaged publicly available programs and so has Moblin.. and Fedora and Mandriva and so on.
What specifically do you mean by a "KDE and Debian program"?
I'm pretty sure I tried to run "dpkg -i" on moblin just for giggles and got a command not found.
 |
|
2010-02-19
, 20:28
|
|
Posts: 850 |
Thanked: 626 times |
Joined on Sep 2009
@ Vienna, Austria
|
#187
|
Originally Posted by fatalsaint
still...
Anyway.. it's all moot: As long as there already is an ARM port of it somewhere.. it's stupid simple to make either a deb or rpm from it to fit our needs.
one of the benefits of having a huge armel repo is that you also don't have to worry about dependencies much. you take the control file 1:1 and just rebuild what's missing, again not having to fiddle with the packaging files.
i imagine lots of possible errors in package dependencies, multiple packages and so on.
it's not difficult of course, still much easier than porting from scratch, but prone to errors IMHO.
__________________
"What we perceive is not nature itself, but nature exposed to our method of questioning."
-- Werner Karl Heisenberg
"What we perceive is not nature itself, but nature exposed to our method of questioning."
-- Werner Karl Heisenberg
Last edited by SubCore; 2010-02-19 at 20:32. Reason: vocabulary *g*
| The Following 2 Users Say Thank You to SubCore For This Useful Post: | ||
|
|
2010-02-19
, 20:30
|
|
Posts: 3,428 |
Thanked: 2,856 times |
Joined on Jul 2008
|
#188
|
Originally Posted by SubCore
Sure.. any time you add steps you open for more unforeseen circumstances.
it's not difficult of course, still much easier than porting from scratch, but prone to errors IMHO.
It's just, at this point, it's not going to change.. so why bother? Technically, anything we need is still possible.. it's just going to require a little more work to get it to where we need it.
|
|
2010-02-19
, 20:55
|
|
Posts: 992 |
Thanked: 995 times |
Joined on Dec 2009
@ California
|
#189
|
Originally Posted by fatalsaint
Because sources are maintained not from RPM but from developers sites which take care about all distributions.
Why would RPM sources have the change when their distro doesn't cross-compile or maintain an active ARM repo?
Source RPMs (or DEBs) have a big sense for system management software like start/stop interface, catching mesg about unlocking device etc. And that sources are pretty uniq to architecture ... well to a specific distribution, actually... big and reach repos from other distributions don't help too much here...
| The Following User Says Thank You to egoshin For This Useful Post: | ||
 |
|
2010-02-19
, 21:08
|
|
Posts: 445 |
Thanked: 572 times |
Joined on Oct 2009
@ Oxford
|
#190
|
Originally Posted by egoshin
Not so much. Quite often distribution packages carry patches that upstream hasn't taken, or indeed has refused to take. If upstream doesn't care about arm support (and a lot don't) it is quite possible that Debian is one of the few places that will have code that compiles for arm.
Because sources are maintained not from RPM but from developers sites which take care about all distributions.
| The Following User Says Thank You to ewan For This Useful Post: | ||
 |
| Tags |
| rabble-rousing, rpm vs. deb war, rpmligion vs debligion, vote attila77 |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 20:25.
The only exclusion - if you port a system maintenance application which works in the same model as your debian-based system AND your window manager. So, Gnome vs KDE plays role but DEB vs RPM - not.