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#48201 - [scite] Doesn't install includes

Attached to Project: Community Packages
Opened by Daurnimator (daurnimator) - Tuesday, 16 February 2016, 05:07 GMT
Last edited by Alexander F. Rødseth (xyproto) - Sunday, 21 February 2016, 21:36 GMT
Task Type Feature Request
Category Upstream Bugs
Status Closed
Assigned To Alexander F. Rødseth (xyproto)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Headers are not currently part of the package.
I'd expect files in 'include' dir to be installed to /usr/include/scintilla or similar
This task depends upon

Closed by  Alexander F. Rødseth (xyproto)
Sunday, 21 February 2016, 21:36 GMT
Reason for closing:  Upstream
Comment by Doug Newgard (Scimmia) - Tuesday, 16 February 2016, 05:21 GMT
Why would a program need includes?
Comment by Daurnimator (daurnimator) - Tuesday, 16 February 2016, 05:35 GMT
Good point, I forgot to document my thought process:

The source tarball should really have multiple package outputs:
- 'scintilla-gtk' library
- 'scite-gtk' (what is currently packaged as 'scite')
- 'scintilla-edit-base-qt'
- 'scintilla-edit-qt'
- 'scintilla-edit-py-qt'

To create a plugin for scite, I need the headers from what I'd call 'scintilla-gtk' library (which are globally visible when loaded inside the scite binary)
Comment by Alexander F. Rødseth (xyproto) - Saturday, 20 February 2016, 21:08 GMT
Two points:

* Other editors usually let developers write plugins in scripting languages, which solves this issue.

* Packages that include header files are usually libraries, not applications.

But the main thing here, is that:

* The default vanilla installation process (which is what Arch uses) is "make install", and it does not include the header files.

Please report this upstream, to the scite developers, if you wish the standard installation process of scite to include these files.

Loading...