Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#26568 - [gtk2hs-pango]: Consider renaming package

Attached to Project: Community Packages
Opened by Magnus Therning (magus) - Saturday, 22 October 2011, 14:46 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 25 October 2011, 20:05 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Please consider renaming this package to 'haskell-pango' so that it follows the naming convention for all other haskell library packages in Arch.
This task depends upon

Closed by  Sergej Pupykin (sergej)
Tuesday, 25 October 2011, 20:05 GMT
Reason for closing:  Implemented
Comment by Sergej Pupykin (sergej) - Tuesday, 25 October 2011, 14:26 GMT
I suggest haskell-gtk2hs-pango, because of project name is gtk2hs:

http://projects.haskell.org/gtk2hs/
Comment by Sergej Pupykin (sergej) - Tuesday, 25 October 2011, 14:40 GMT
No, lets pango will be haskell-pango. Only gtk2hs-buildtools will be haskell-gtk2hs-buildtools.

I'll rename package according to homepage url ttp://hackage.haskell.org/package/<NAME>;
Comment by Magnus Therning (magus) - Tuesday, 25 October 2011, 18:22 GMT
Yes, let pango become haskell-pango.

Please don't rename gtk2hs-buildtools, it already follows the naming standard since it isn't a haskell library.

Loading...