Re: Dropping maintainership of devel/allegro and devel/allegro-devel

2012-08-16 Thread Pierre-Jacques MIMIFIR
Dear Naram,

If you're interested.
I can make a new update for these two ports, maybe in next 2 weeks, the
taget will probably is 4.4.2.

Best Regards,
Pierre-Jacques MIMIFIR

2012/8/16 Jason Helfman j...@freebsd.org

 -- Forwarded message --
 From: Ruslan Mahmatkhanov cvs-...@yandex.ru
 Date: Wed, Aug 15, 2012 at 9:56 PM
 Subject: Re: Dropping maintainership of devel/allegro and
 devel/allegro-devel
 To: Naram Qashat cyberb...@cyberbotx.com
 Cc: freebsd-ports@freebsd.org


 Naram Qashat wrote on 16.08.2012 04:41:

  I've realized that ever since I took over maintaining these two ports, I
 haven't kept them maintained.  I am wanting to drop these two ports, if
 anyone else wishes to become their maintainers, I am perfectly fine with
 it.

 Thanks,
 Naram Qashat


 Done.

 --
 Regards,
 Ruslan

 Hi,

 I just noticed that you put a new port in for a similarly dropped
 maintainership of the ports
 in the subject.
 Would you be interested in maintaining these?

 Thanks!
 -jgh

 --
 Jason Helfman  | FreeBSD Committer
 j...@freebsd.org | http://people.freebsd.org/~jgh




___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


net-p2p/tribler update from 5.5.24_1 to version 5.9.27 please

2012-08-16 Thread bugs bunny
I would very much appreciate it if someone will update Tribler 5.5.24_1 to 
version 5.9.27. Thank you very much.

http://www.freshports.org/net-p2p/tribler/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


FreeBSD Port: misc/mc-light

2012-08-16 Thread Alexander Efimov
Hi

found this typo in Makefile, while trying to make mc-light with working
subshell:

in current Makefile we have this if subshell defined we make mc without
subshell actually

.if ${PORT_OPTIONS:MSUBSHELL}
CONFIGURE_ARGS+=--without-subshell
.endif

as it was in older makefile

.if !defined(WITH_SUBSHELL)
CONFIGURE_ARGS+=--without-subshell
.endif


best regards
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Get ports tree of the current pkgng repository

2012-08-16 Thread Michael Schnell

Hi,
I don't know if this came up already, but not as far as I know. So, I
was thinking it would be nice to add a mechanism to pkgng, which enables
the user to get the ports tree corresponding to the current repository.

At least I've the problem that I really like the idea of the pkgng
system, but I need a few custom build packages. For instance rawtherapee
is not working for me with OpenMP, so I have to disable it to get it
working, or I made some patches for openbox, which of course then needs
to be compiled. In order to get not in conflict with a more recent
ports tree the exact version of the repository build would be nice.

At the moment I can think of two ways to implement it. The easiest way
would be to add the ports tree as a packages into the repository. A more
complicated thing is to add a mechanism to portsnap synchronised with
the pkgng system to direct fetch it, or at least a revision number of
the current repo, so you can check it out of the subversion.

How do you guys feel about this?


Greetings
Michael

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: Dropping maintainership of devel/allegro and devel/allegro-devel

2012-08-16 Thread Jason Helfman

Following the top-posting :(

Pierre-Jacques - Naram no longer maintains these ports. Would you like me to
assign maintainer-ship to you?

Thanks!

-jgh

On Thu, Aug 16, 2012 at 11:19:27AM +0200, Pierre-Jacques MIMIFIR thus spake:

Dear Naram,

If you're interested.
I can make a new update for these two ports, maybe in next 2 weeks, the
taget will probably is 4.4.2.

Best Regards,
Pierre-Jacques MIMIFIR

2012/8/16 Jason Helfman j...@freebsd.org


-- Forwarded message --
From: Ruslan Mahmatkhanov cvs-...@yandex.ru
Date: Wed, Aug 15, 2012 at 9:56 PM
Subject: Re: Dropping maintainership of devel/allegro and
devel/allegro-devel
To: Naram Qashat cyberb...@cyberbotx.com
Cc: freebsd-ports@freebsd.org


Naram Qashat wrote on 16.08.2012 04:41:

 I've realized that ever since I took over maintaining these two ports, I

haven't kept them maintained.  I am wanting to drop these two ports, if
anyone else wishes to become their maintainers, I am perfectly fine with
it.

Thanks,
Naram Qashat



Done.

--
Regards,
Ruslan

Hi,

I just noticed that you put a new port in for a similarly dropped
maintainership of the ports
in the subject.
Would you be interested in maintaining these?

Thanks!
-jgh

--
Jason Helfman  | FreeBSD Committer
j...@freebsd.org | http://people.freebsd.org/~jgh





___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org



--
Jason Helfman
System Administrator
experts-exchange.com
http://www.experts-exchange.com/M_4830110.html
E4AD 7CF1 1396 27F6 79DD  4342 5E92 AD66 8C8C FBA5
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: Get ports tree of the current pkgng repository

2012-08-16 Thread Kimmo Paasiala
On Thu, Aug 16, 2012 at 10:56 PM, Michael Schnell s-...@s-tlk.org wrote:
 Hi,
 I don't know if this came up already, but not as far as I know. So, I
 was thinking it would be nice to add a mechanism to pkgng, which enables
 the user to get the ports tree corresponding to the current repository.

 At least I've the problem that I really like the idea of the pkgng
 system, but I need a few custom build packages. For instance rawtherapee
 is not working for me with OpenMP, so I have to disable it to get it
 working, or I made some patches for openbox, which of course then needs
 to be compiled. In order to get not in conflict with a more recent
 ports tree the exact version of the repository build would be nice.

 At the moment I can think of two ways to implement it. The easiest way
 would be to add the ports tree as a packages into the repository. A more
 complicated thing is to add a mechanism to portsnap synchronised with
 the pkgng system to direct fetch it, or at least a revision number of
 the current repo, so you can check it out of the subversion.

 How do you guys feel about this?


 Greetings
 Michael


Why not just include the SVN revision of the ports tree that was used
to create the packages in the package metadata?

-Kimmo
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: Get ports tree of the current pkgng repository

2012-08-16 Thread Kimmo Paasiala
On Fri, Aug 17, 2012 at 6:25 AM, Kimmo Paasiala kpaas...@gmail.com wrote:
 On Thu, Aug 16, 2012 at 10:56 PM, Michael Schnell s-...@s-tlk.org wrote:
 Hi,
 I don't know if this came up already, but not as far as I know. So, I
 was thinking it would be nice to add a mechanism to pkgng, which enables
 the user to get the ports tree corresponding to the current repository.

 At least I've the problem that I really like the idea of the pkgng
 system, but I need a few custom build packages. For instance rawtherapee
 is not working for me with OpenMP, so I have to disable it to get it
 working, or I made some patches for openbox, which of course then needs
 to be compiled. In order to get not in conflict with a more recent
 ports tree the exact version of the repository build would be nice.

 At the moment I can think of two ways to implement it. The easiest way
 would be to add the ports tree as a packages into the repository. A more
 complicated thing is to add a mechanism to portsnap synchronised with
 the pkgng system to direct fetch it, or at least a revision number of
 the current repo, so you can check it out of the subversion.

 How do you guys feel about this?


 Greetings
 Michael


 Why not just include the SVN revision of the ports tree that was used
 to create the packages in the package metadata?

 -Kimmo

And of course in the repository metadata as you proposed, sorry not
enough coffee yet :P

-Kimmo
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org