Opened 7 years ago
Last modified 7 years ago
#44246 new submission
[NEW] webkitkde submission
| Reported by: | RJVB (René Bertin) | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | NicosPavlov, mkae (Marko Käning) | |
| Port: | webkitkde |
Description
Please find attached a portfile for the webkitkde project, which makes QtWebKit framework available to KDE apps and includes a KPart allowing konqueror to use said framework.
webkitkde being in development with only a git repository I based my portfile on the snapshots provided by Ubuntu in one of its official packages (for "Utopic Unicorn" to be exact). The portfile should track upstream releases and package revisions.
Attachments (1)
Change History (5)
comment:1 Changed 7 years ago by mkae (Marko Käning)
| Cc: | nicos@… mk@… added; nicos removed |
|---|---|
| Port: | webkitkde added |
| Summary: | webkitkde submission → [NEW] webkitkde submission |
| Version: | 2.3.1 |
comment:2 Changed 7 years ago by NicosPavlov
comment:3 Changed 7 years ago by RJVB (René Bertin)
I noticed that when building kde4-baseapps, konqueror is set by default with webkitkde instead of khtml. This type of opportunistic settings should be solved in order to have a consistent behaviour. This should
I think that's by design. In my experience on Linux, Webkit does work/perform better than khtml (not illogical as it's the successor of sorts).
specially solved in this case, considering that webkitkde is announced as potentially unstable.
I've seen but never noticed anything to support that claim.
R
comment:4 Changed 7 years ago by petrrr
| Keywords: | kde web removed |
|---|
I noticed that when building kde4-baseapps, konqueror is set by default with webkitkde instead of khtml. This type of opportunistic settings should be solved in order to have a consistent behaviour. This should specially solved in this case, considering that webkitkde is announced as potentially unstable.