[haiku-bugs] Re: [Haiku] #9825: package information are too restrictive

  • From: "X512" <trac@xxxxxxxxxxxx>
  • Date: Wed, 19 Jun 2013 07:39:25 -0000

#9825: package information are too restrictive
---------------------------+-----------------------------------
   Reporter:  X512         |      Owner:  nobody
       Type:  enhancement  |     Status:  new
   Priority:  normal       |  Milestone:  R1
  Component:  - General    |    Version:  R1/Package Management
 Resolution:               |   Keywords:
 Blocked By:               |   Blocking:
Has a Patch:  0            |   Platform:  All
---------------------------+-----------------------------------

Comment (by X512):

 Replying to [comment:3 bonefish]:
 > The package file name isn't something a user usually comes in contact
 with. It isn't meant for user friendly reading. Instead it encodes
 important information like the package version and architecture. Package
 files may also be stored on systems other than Haiku and may be
 transferred via various protocols. Sticking to ASCII characters without
 whitespace avoids potential character encoding and quoting/escaping
 issues.
 But why it should limit package name (not file name) itself? Also why
 package name should be same as in file name?

 > I don't know what distribution conditions you're thinking of. Generally
 it might be interesting even for a commercial company to provide a
 repository, so that bug fix updates can be delivered automatically to the
 user. If, for some reason, they want to provide only the package file
 itself, they could build one per target language with the respectively
 translated meta information.
 Commertical software is usually not free to download (but downloadable
 software with activation exists, shareware for example). Package can be
 transfered to the user only after being paid by some sequre method or even
 by physical media such as CD-ROM. Mayble this is obsolete information
 because I don't buy software often and prefer free software.

 > As written before, we haven't really worked out how exactly we want to
 handle localization. We may also provide some way to build all
 translations into a package.
 Anyway this should be made before package manamement became part of Haiku
 release officially.

 > That would require the package info file to be changed and the package
 to be rebuilt whenever a translation is added or a typo is fixed in any of
 them. I think generally we should keep the translations separate from the
 package.
 Package names should be translated for listing installed packages as I
 mentioned before.

--
Ticket URL: <http://dev.haiku-os.org/ticket/9825#comment:4>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

Other related posts: