Bug 229991 - [new port] x11-toolkits/vte-ng: Enhanced replacement for the standard vte library
Summary: [new port] x11-toolkits/vte-ng: Enhanced replacement for the standard vte lib...
Status: Closed Not Accepted
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Tobias Kortkamp
URL:
Keywords:
Depends on:
Blocks: 229992
  Show dependency treegraph
 
Reported: 2018-07-23 20:41 UTC by Matthew Stobbs
Modified: 2018-10-24 12:02 UTC (History)
2 users (show)

See Also:


Attachments
x11-toolkits/vte-ng as a port (8.63 KB, patch)
2018-07-23 20:41 UTC, Matthew Stobbs
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Stobbs 2018-07-23 20:41:09 UTC
Created attachment 195399 [details]
x11-toolkits/vte-ng as a port

In order to include termite (a lightweight vte based terminal emulator), a more modern vte was needed. This is that library.
Comment 1 Nathan 2018-09-01 01:43:40 UTC
Builds fine on 12-Current AMD64, though you need to strip the binary or add:
INSTALL_TARGET= install-strip
Comment 2 Tobias Kortkamp freebsd_committer freebsd_triage 2018-10-17 15:28:48 UTC
No feedback for 1.5 months after comment #1.  Matthew, are you still
interested in this port?

This could also use a reconfirmation that it still builds after the
GNOME 3.28 import.
Comment 3 Tobias Kortkamp freebsd_committer freebsd_triage 2018-10-24 12:00:28 UTC
Closing this as rejected.

- No feedback for too long now

- Upstream has not seen any updates in 2 years

- vte-ng conflicts with vte3 on installed files.  Both install
  libvte-2.91.so for example.  Since we do not have an alternatives
  system in the ports tree this will cause conflicts with many other
  ports that are part of normal desktop installations to the point
  of not being very useful.
Comment 4 Tobias Kortkamp freebsd_committer freebsd_triage 2018-10-24 12:02:26 UTC
(In reply to Tobias Kortkamp from comment #3)
> - Upstream has not seen any updates in 2 years

Not true.  I didn't look at the other branches and the issue tracker.