[gentoo-dev] new ebuilds

[gentoo-dev] new ebuilds

[Parag Mehta]

[-- Attachment #1: Type: text/plain, Size: 278 bytes --]

Hi,

can somebody with cvs access commit the attaached the ebuilds for me, please.

the nmap ebuild has been modifed as per suggestions recvd. from ben & achim.
the pure-ftpd ebuild is for the new release of the app and recommended one.

regards,

pm
--
Gentoo Linux Developer


[-- Attachment #2: nmap-2.54_beta26.ebuild --]
[-- Type: text/plain, Size: 818 bytes --]

# Copyright 1999-2000 Gentoo Technologies, Inc.
# Distributed under the terms of the GNU General Public License, v2 or later
# Author Parag Mehta <pm@gentoo.org>

P=nmap-2.54BETA26
A=${P}.tgz
S=${WORKDIR}/${P}
DESCRIPTION="Portscanner"
SRC_URI="http://www.insecure.org/nmap/dist/"${A}
HOMEPAGE="http://www.insecure.org/nmap/"

DEPEND="virtual/glibc
	gtk? ( >=x11-libs/gtk+-1.2.8 )"

src_compile() {                           
  try ./configure --host=${CHOST} --prefix=/usr --mandir=/usr/share/man --enable-ipv6
  if [ "`use gtk`" ] ; then
    try make
  else
    try make nmap
  fi
}

src_install() {                               

  try make prefix=${D}/usr mandir=${D}/usr/share/man install

  dodoc CHANGELOG COPYING HACKING README*
  cd docs
  dodoc *.txt
  insinto /usr/share/doc/${PF}/html
  doins *.html
}




[-- Attachment #3: pure-ftpd-0.98.8.ebuild --]
[-- Type: text/plain, Size: 1367 bytes --]

# Copyright 1999-2000 Gentoo Technologies, Inc.
# Distributed under the terms of the GNU General Public License, v2 or later
# Author Parag Mehta <pm@gentoo.org>

A=${P}.tar.gz
S=${WORKDIR}/${P}
DESCRIPTION="A Fast Production Quality FTP Server - Bug fixes backported from 0.99 . No new feature. Use this version on production servers."
SRC_URI="http://prdownloads.sourceforge.net/pureftpd/${A}"
HOMEPAGE="http://pureftpd.sourceforge.net"

DEPEND=">=sys-libs/glibc-2.1.3
	>=sys-libs/pam-0.75"

src_compile() {

    cd ${S}
    try ./configure --prefix=/usr  --with-throttling --with-virtualhosts\
	--with-ratios --with-largefile
    try make

}

src_install () {

    cd ${S}
    try make DESTDIR=${D} install
    dodoc COPYING ChangeLog README README.Configuration-File 
    dodoc README.Contrib README.LDAP README.Netfilter
    dodir /etc/pure-ftpd
    echo "Please do no forget to run, the following syntax :"
    echo "ebuild pure-ftpd-0.98.8.ebuild config"
    echo "This will add the necessary post install config to your system."
}

pkg_config() {
	echo "This config script will add pftpd lines to your /etc/xinetd.conf."
	echo "Press control-C to abort, hit Enter to continue."
	echo
	read
	cat ${FILESDIR}/pftpd.inetd >> ${ROOT}etc/inetd.conf
	ln -s /dev/null /etc/pure-ftpd/127.0.0.1
	/etc/rc.d/init.d/svc-xinetd restart
	echo "Modifications applied."
}

[gentoo-dev] New ebuilds

[Philippe Lafoucrière]

hey devs
Don't kill me too soon... but I really find the way to post new ebuilds
too complicated. I went to bugs.gentoo.org, and got a :

"The 'bug number'  is invalid. It is neither a bug number nor an alias
to a bug number. If you are trying to use QuickSearch, you need to
enable JavaScript in your browser. To help us fix this limitation, add
your comments to bug 70907."

Of course, javascript is enable on my Mozilla Firebird :(

then, I expect nobody is working on the same ebuild as me (a python
module to do some fuzzy logic...).

It's really hard to add the new ebuild. I had to go through the maze of
bugs.gentoo.org. There's no REAL place to add them (no category for new
ebuilds). This part is really "fuzzy" too in
http://www.gentoo.org/doc/en/gentoo-howto.xml with just a link to
bugs.gentoo.org.

I think this should be really simpler, with maybe a new web repository
to upload ebuilds (I know, bugs.gentoo.org is one, but it's too heavy).




--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] New ebuilds

[Philippe Lafoucrière]

By the way, after adding attachments :

Attachment #17964 to Bug #29077 Created 
Status: 400 Bad request (malformed multipart POST) 
Software error:
Undefined subroutine &main::ThrowCodeError called at Bugzilla/CGI.pm line 78.

For help, please send mail to the webmaster (root@localhost), giving
this error message and the time and date of the error.


Software error:
[Fri Sep 19 09:50:28 2003] processmail: Undefined subroutine &main::ThrowCodeError called at Bugzilla/CGI.pm line 78.
Compilation failed in require at ./processmail line 31.

For help, please send mail to the webmaster (root@localhost), giving
this error message and the time and date of the error.

Note: Bugzilla automatically detected the content type
application/octet-stream for this attachment. If this is incorrect,
correct the value by editing the attachment. 



--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] New ebuilds

[Georgi Georgiev]

On 19/09/2003 at 11:51:45(+0200), Philippe Lafoucrière used 1.0K just to say:
> hey devs
> Don't kill me too soon... but I really find the way to post new ebuilds
> too complicated. I went to bugs.gentoo.org, and got a :
> 
> "The 'bug number'  is invalid. It is neither a bug number nor an alias
> to a bug number. If you are trying to use QuickSearch, you need to
> enable JavaScript in your browser. To help us fix this limitation, add
> your comments to bug 70907."

http://bugs.gentoo.org/show_bug.cgi?id=29065

-- 
/\   Georgi Georgiev   /\ Subtlety is the art of saying what you think /\
\/    chutz@gg3.net    \/ and getting out of the way before it is      \/
/\  +81(90)6266-1163   /\ understood.                                  /\

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] New ebuilds

[Georgi Georgiev]

On 19/09/2003 at 12:02:07(+0200), Philippe Lafoucrière used 0.9K just to say:
> By the way, after adding attachments :
> 
> Attachment #17964 to Bug #29077 Created 
> Status: 400 Bad request (malformed multipart POST) 
> Software error:
> Undefined subroutine &main::ThrowCodeError called at Bugzilla/CGI.pm line 78.
> 
> For help, please send mail to the webmaster (root@localhost), giving
> this error message and the time and date of the error.
> 
> 
> Software error:
> [Fri Sep 19 09:50:28 2003] processmail: Undefined subroutine &main::ThrowCodeError called at Bugzilla/CGI.pm line 78.
> Compilation failed in require at ./processmail line 31.
> 
> For help, please send mail to the webmaster (root@localhost), giving
> this error message and the time and date of the error.
> 
> Note: Bugzilla automatically detected the content type
> application/octet-stream for this attachment. If this is incorrect,
> correct the value by editing the attachment. 

Actually, despite the error message, the attachment was probably attached.

-- 
(*   Georgi Georgiev   (* Just because you like my stuff doesn't mean  (*
*)    chutz@gg3.net    *) I owe you anything. -- Bob Dylan             *)
(*  +81(90)6266-1163   (*                                              (*

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] New ebuilds

[Patrick Kursawe]

[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]

On Fri, Sep 19, 2003 at 11:51:45AM +0200, Philippe Lafoucrière wrote:
> Don't kill me too soon... but I really find the way to post new ebuilds
> too complicated. I went to bugs.gentoo.org, and got a :
> 
> "The 'bug number'  is invalid. It is neither a bug number nor an alias
> to a bug number. If you are trying to use QuickSearch, you need to
> enable JavaScript in your browser. To help us fix this limitation, add
> your comments to bug 70907."

Where did you click? The above "I went to ... and got a ..." is not
exactly a useful bug report...

> It's really hard to add the new ebuild. I had to go through the maze of
> bugs.gentoo.org. There's no REAL place to add them (no category for new
> ebuilds). This part is really "fuzzy" too in
> http://www.gentoo.org/doc/en/gentoo-howto.xml with just a link to
> bugs.gentoo.org.

That's why we have http://www.gentoo.org/doc/en/ebuild-submit.xml

> I think this should be really simpler, with maybe a new web repository
> to upload ebuilds (I know, bugs.gentoo.org is one, but it's too heavy).

Even with the guide you didn't find?
I think having new ebuilds coupled to bugzilla is essential because
it provides a method for feedback on the ebuilds in case of problems.

Bye, Patrick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] New ebuilds

[Philippe Lafoucrière]

> Where did you click? The above "I went to ... and got a ..." is not
> exactly a useful bug report...

1- Open bugs.gentoo.org
2- Fill the "Enter a bug # or some search terms:" field with something
like 'fuzzy'
3- Submit


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] New ebuilds

[Philippe Lafoucrière]

> Actually, despite the error message, the attachment was probably attached.

It was


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] New ebuilds

[Philippe Lafoucrière]

> That's why we have http://www.gentoo.org/doc/en/ebuild-submit.xml

Sorry, I didn't see the link ! I thought every thing was in
http://www.gentoo.org/doc/en/gentoo-howto.xml

It's more clear now.

Thank you


--
gentoo-dev@gentoo.org mailing list

[gentoo-dev] New ebuilds

[Rafael Fernández López]

Hi,

I'm not a developer considered in Gentoo project, but I have a little time
that I can give Gentoo everyday. I submitted yesterday tkgate ebuild (new
package in portage), and I am going to start wxmaxima ebuild.

I know that developers are actually busy, and they have lots of things to
do. Those apps are really interesting in sci-mathematics and
sci-electronics respectively, and maybe they'll be taken by a developer
tomorrow, or maybe they are taken 3 months from now...

What I suggest is to take care of this two packages myself, as a developer
(passing all the tests and questions that I have to pass for becoming a
developer), and I'd like to know if somebody can mentor me.

What I did before creating this ebuild was to search some bugs and post
them or search them in the source code. I don't usually post bugs before
reading source code, and when I post it, I suggest where in the source
code the bug can live... Is the way I normally work.

And by the way... I'm a GPL fighter... fighting for our rights.

Another thing... I normally have little time for searching bugs, creating
ebuilds and so on... but I'm a student (at University) and I may have
enough time for fixing bugs that always appear on packages... so this is
my proposal.

Thanks,
Rafael Fernández López.
-- 
gentoo-dev@gentoo.org mailing list