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

  • From: "X512" <trac@xxxxxxxxxxxx>
  • Date: Wed, 19 Jun 2013 05:05:43 -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:1 bonefish]:
 > Package description and license are intentionally mandatory, since we'd
 like to avoid packages that no one knows what they are about and in which
 way one is allowed to use them. If you're building a package just for
 yourself, you can just specify dummy values for these attributes.
 Summary field is probably enougth, there are no need to force write long
 description. License sometimes is unknown and can't be provided (for
 example author of program didn't mentioned licence). Also not all licenses
 are called or called generally such as "EULA". Will this introduce name
 conflict or not?

 > The package name is intentionally restricted. It is also encoded in the
 package file name, so white space and non-ASCII characters would be
 annoying. Maybe we should introduce a "display name" attribute.
 Why file name should be dublicated inside a package itself? Also spaces
 and Unicode characters are OK in filenames (excluding FAT12 and other
 ancient filesystems).

 Personally I'm strictly against "computer" file names and always call
 files with natural names.

 > Description and summary should indeed be localizable. We haven't worked
 out how we'll handle that. The translations will very likely not end up in
 the package file itself or in the package info, since that would just add
 unnecessarily to the package size. We'll most likely implement that at the
 repository level.
 Packages musn't be stored in a repository. For example it can be provided
 by some commertical corporation with special distribufion conditions.

 Why not localize PackageInfo itself? for example by edding ":<language
 id>" to the end of each localizable field?

 For example:


 {{{
 name = Haiku
 description:en = "Haiku is a new open-source operating system that
 specifically targets personal computing. Inspired by the BeOS, Haiku is
 fast, simple to use, easy to learn and yet very powerful."
 description:jp = "Haiku はパーソナル・コンピューティング向け、新しいオペレ
 ーティングシステムです。......"
 ...
 }}}


 At least package name should be localizable for listing installed
 packages. Other fields can be localized in repository (or moved completly
 in repository because this information ia already presented in readme,
 documentation etc.; user will probably read package description only in
 repository). Only application names should be localized, library package
 names are not localized.

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

Other related posts: