[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    RE: Most tarballs come with RPM specs (was: Easier method
From:       "Carlos Leonhard Woelz" <carloswoelz () imap-mail ! com>
Date:       2004-01-09 20:12:10
Message-ID: 20040109201210.6498945560 () server1 ! messagingengine ! com
[Download RAW message or body]


On Fri,  9 Jan 2004 19:13:27 +0000, een3sae@leeds.ac.uk said:
> It seems to me the biggest problem that would be faced in making the tool
> I 
> have described above would largely be one of integration; by no means
> trivial, 
> but fortunately most of the code required to make the tool I have
> suggested 
> above seems to exist in Linux already in one form or another and would be
> able 
> to be reused - someone just needs to bring these separate parts together
> with 
> a common interface etc. 
>  
> What do you guys think? In fact in 6 months time when I have learnt how
> to 
> code I might even have a bash at this one myself! 
>  
> -=+Stephen Ellwood+=- 

Hi Stephen,

It's very nice of you to propose a new feature and try to code it
yourself!
I suggest taking a look on kdialogs, thay and be easily on scripts.

But

- There is a plethora of distributions and packages formats. This is not
a question of supporting rpms only. Maybe it is easier to start
supporting your distribution format (rpm I imagine). (BTW, Linux is not
the only operational system supported by KDE).
- The rpm and deb install tools perform some checks before installing
stuff, like if there are no conflicts, if all dependencies are fulfilled.
Making and installing tarballs can be very dangerous if someone don't
know what he is doing. Usually is experimental software, it is a very raw
way to distribute software. Many times the compile fails. The compile
process gives you information about why it failed, but sometimes it is
not easy to interpret it if you don't know the code. If these procedures
were easy, there would be no reason to create package formats. They exist
to solve these problems.

It is _hard_ to create tools that work all the time. It is easy to create
a hack that will work with 50% of the cases. Users would not accept the
second case, as it would invite people to try and then to be
dissapointed.

But a new tool is always welcome!

Cheers,
-- 
  Carlos Leonhard Woelz
  carloswoelz@imap-mail.com

-- 
http://www.fastmail.fm - Sent 0.000002 seconds ago
_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread]