From: George Shapovalov <georges@its.caltech.edu>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Netscape Packages
Date: Fri, 12 Apr 2002 12:05:15 -0700 [thread overview]
Message-ID: <200204121205.15245.georges@its.caltech.edu> (raw)
In-Reply-To: <3CB7285B.2060004@netscape.com>
If you would like to see Netscape 6 in gentoo and are willing to spend some
time on it, please do contribute by any means.
Now to the technical stuff.
You do not need to know many details about portage code. What is getting
submitted is a set of build instructions wrapped in a bash script (and as
such, the tarball itself will not help much).
Please see:
http://www.gentoo.org/doc/gentoo-howto.html
for a description on how to create such an ebuild
(bash script (quite often very basic) containing install instructions). You
can also look at ebuilds for other packages.
The ebuild and any necessary supplementary files (patches, etc) are to be
submitted to http://bugs.gentoo.org, this page contains an ebuild submission
description:
http://www.gentoo.org/doc/ebuild-submit.html.
If you still do not feel like creating an ebuild file (BTW you can always go
to #gentoo channel at irc.openprojects.net to get some real-time ebuild
creation assistance) you can instead submit build instructions and any url
pointers to bugs.gentoo.org as a feature request ( but this will take more
time to process for obvious reasons :)).
George
On Friday 12 April 2002 11:32, John Dee wrote:
> I was looking at your netscape packages, and was wondering why you guys
> weren't using the 6.x series. The reason I ask, is that the 4.x series
> probably won't have another release (I'm the *NIX build engineer on the
> project).
> I'm also one of the build engineers on the 6.x project.
> Also, if needed, I could make a 6.x package for you guys. It really
> wouldn't take much to do.
> The only thing that might be a problem is the fact I don't know portage
> yet (I've been using gentoo a total of about 3 days).
> I *COULD* supply you guys with a tarball, and instructions, if you want.
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2002-04-12 19:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-12 18:32 [gentoo-dev] Netscape Packages John Dee
2002-04-12 19:05 ` George Shapovalov [this message]
2002-04-12 19:25 ` John Dee
2002-04-12 19:30 ` Jared H. Hudson
2002-04-12 19:34 ` John Dee
2002-04-12 19:40 ` Jared H. Hudson
2002-04-12 19:42 ` Jim Nutt
2002-04-12 20:10 ` Thilo Bangert
2002-04-12 20:17 ` Jim Nutt
2002-04-12 20:25 ` John Dee
2002-04-13 6:24 ` [gentoo-dev] " Paul
2002-04-12 19:40 ` [gentoo-dev] " Avi Schwartz
2002-04-12 19:52 ` John Dee
2002-04-12 20:11 ` George Shapovalov
2002-04-12 20:04 ` George Shapovalov
2002-04-13 4:38 ` Edward Muller
2002-04-12 19:30 ` Tod M. Neidt
2002-04-12 19:05 ` John Dee
2002-04-12 22:19 ` Spider
2002-04-12 22:25 ` John Dee
2002-04-12 22:31 ` Spider
-- strict thread matches above, loose matches on Subject: below --
2002-04-12 19:39 Sean Mitchell
2002-04-12 19:40 ` John Dee
2002-04-12 19:47 ` Jim Nutt
2002-04-12 20:19 ` Terje Kvernes
2002-04-12 22:24 ` Spider
2002-04-13 2:08 ` Bill Kenworthy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200204121205.15245.georges@its.caltech.edu \
--to=georges@its.caltech.edu \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox