| View previous topic :: View next topic |
| Author |
Message |
charles17
Advocate
Joined: 02 Mar 2008
Posts: 3664
|
 Posted: Thu Mar 17, 2016 4:47 pm Post subject: www-client/servo - a new browser |
 |
|
I am trying to create an ebuild for the pre alpha of servo.
What I have is a basic skeleton just allowing the download and ebuild unpack.
| Code: | # Copyright 1999-2016 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $
EAPI=6
inherit git-r3
DESCRIPTION="Servo, the Parallel Browser Engine Project"
HOMEPAGE="https://servo.org"
EGIT_REPO_URI="https://github.com/servo/servo.git"
LICENSE="MPL-2.0"
SLOT="0"
KEYWORDS="~amd64" |
As you can see most stuff is still missing. Just started to work through Ebuild Writing.
Your tips are very much appreciated as this is my very first ebuild.
Questions- How can I verify the download? Can't find any signatures or checksums upstream.
- How to get rid of the bundled Rust compiler in favour of using dev-lang/rust?
- Where to find which arches to keyword except ~amd64?
- How to find out the exact minimal versions of dependencies already given by upstream?
| From upstream: https://github.com/servo/servo#user-content-prerequisites wrote: | On Gentoo Linux:
sudo emerge net-misc/curl media-libs/freeglut \
media-libs/freetype media-libs/mesa dev-util/gperf \
dev-python/virtualenv dev-python/pip dev-libs/openssl \
x11-libs/libXmu media-libs/glu x11-base/xorg-server |
|
|
| Back to top |
|
 |
Perfect Gentleman
Veteran
Joined: 18 May 2014
Posts: 1249
|
| Posted: Thu Mar 17, 2016 6:16 pm Post subject: |
|
|
| it's not a browser, it's engine |
|
| Back to top |
|
|
khayyam
Watchman
Joined: 07 Jun 2012
Posts: 6227
Location: Room 101
|
| Posted: Thu Mar 17, 2016 8:01 pm Post subject: Re: www-client/servo - a new browser |
|
|
| charles17 wrote: | | [*]How can I verify the download? Can't find any signatures or checksums upstream. |
charles ... it's git, so checkusm'd.
| charles17 wrote: | | [*]How to get rid of the bundled Rust compiler in favour of using dev-lang/rust? |
That will probably require a patch or various sed one-liners in pkg_setup() ... it somewhat depends on the build system, so, wherever the version, path/to, etc, of rust is defined.
| charles17 wrote: | | [*]Where to find which arches to keyword except ~amd64? |
Don't ... only ~arch for those arches which you've successfully merged ... other arches can keyword '**' if they want to emerge without it being keyworded.
| charles17 wrote: | | [*]How to find out the exact minimal versions of dependencies already given by upstream? |
I wouldn't place a grain of trust on that list, these are the sort of "instructions" that should be ignored (and you can tell that by the provided command). Anyhow, again this depends on the build system, is pkgconfig used, etc, what is the defined in configure, or Makefile, or autoconf.
best ... khay |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Unsupported Software
