Any objections?
On Mon Jan 01, 2018 at 03:21:37PM +0100, Rafael Sadowski wrote:
> Hi All,
>
> please find below a simple diff to update doxygen. There are a three
> notables changes:
>
> - Remove the DOXYGEN_ENCODE_PATH_STRIP hack diff. No port uses it anymore
> - Change MAINTAINER email
Hi All,
please find below a simple diff to update doxygen. There are a three
notables changes:
- Remove the DOXYGEN_ENCODE_PATH_STRIP hack diff. No port uses it anymore
- Change MAINTAINER email address
- CONFIGURE_ARGS and BUILD_DEPENDS tweaks
The only one consumer opencv builds fine and
*ping*
On Sat Mar 25, 2017 at 09:06:35AM +0100, Rafael Sadowski wrote:
> Hi All,
>
> straightforward update to the last doxygen version. After all
> problematic doxygen ports have been modified, the doxygen update is
> ready. The following ports still use it but there are no PLIST changes:
>
>
Hi All,
straightforward update to the last doxygen version. After all
problematic doxygen ports have been modified, the doxygen update is
ready. The following ports still use it but there are no PLIST changes:
astro/stellarium
audio/liblo
audio/libnjb
databases/soprano
devel/simulavr
devel/tclap
On 11/13/16 22:54, Jeremie Courreges-Anglas wrote:
> Jeremie Courreges-Anglas writes:
>
>> Stuart Henderson writes:
>
> [...]
>
>>> 3. split the gui off to a different port. keep the same pkgname stem,
>>> so it just needs an @pkgpath in PLIST for
Jeremie Courreges-Anglas writes:
> Stuart Henderson writes:
[...]
>> 3. split the gui off to a different port. keep the same pkgname stem,
>> so it just needs an @pkgpath in PLIST for updates to work.
>
> I'd prefer this option.
In the meantime, let's
Stuart Henderson writes:
> On 2016/11/13 21:26, Nigel Taylor wrote:
>> >
>> I will not be able to test building that for sometime as in middle of
>> dpb run, I would say that it will fail. Not proved, but the estdc++ in
>> the wantlib requires the library to be installed,
On 2016/11/13 21:26, Nigel Taylor wrote:
> >
> I will not be able to test building that for sometime as in middle of
> dpb run, I would say that it will fail. Not proved, but the estdc++ in
> the wantlib requires the library to be installed, that requires a
> dependency set by x11/qt5.port.mk,
>
On 11/13/16 19:50, Rafael Sadowski wrote:
> On Sat Nov 12, 2016 at 11:17:18PM +0100, Jeremie Courreges-Anglas wrote:
>> Nigel Taylor writes:
>>
>>> On 10/22/16 16:42, Rafael Sadowski wrote:
On Tue Sep 20, 2016 at 01:33:34AM +0100, Stuart Henderson wrote:
>
Nigel Taylor writes:
> On 10/22/16 16:42, Rafael Sadowski wrote:
>> On Tue Sep 20, 2016 at 01:33:34AM +0100, Stuart Henderson wrote:
>>> These plist changes for every update are getting silly, I think I'd
>>> rather disable doxygen in those ports..
>>>
>>
>> Other
On 10/22/16 16:42, Rafael Sadowski wrote:
> On Tue Sep 20, 2016 at 01:33:34AM +0100, Stuart Henderson wrote:
>> These plist changes for every update are getting silly, I think I'd
>> rather disable doxygen in those ports..
>>
>
> Other opinions or agreements?
>
I don't build qt5/kde4/kde5 for
On 2016/11/10 11:31, Jeremie Courreges-Anglas wrote:
> Rafael Sadowski writes:
>
> > On Tue Sep 20, 2016 at 01:33:34AM +0100, Stuart Henderson wrote:
> >> These plist changes for every update are getting silly, I think I'd
> >> rather disable doxygen in those ports..
> >>
Rafael Sadowski writes:
> On Tue Sep 20, 2016 at 01:33:34AM +0100, Stuart Henderson wrote:
>> These plist changes for every update are getting silly, I think I'd
>> rather disable doxygen in those ports..
>>
>
> Other opinions or agreements?
I propose that we first see
Hi,
Rafael Sadowski wrote:
> On Tue Sep 20, 2016 at 01:33:34AM +0100, Stuart Henderson wrote:
>> These plist changes for every update are getting silly, I think I'd
>> rather disable doxygen in those ports..
>>
>
> Other opinions or agreements?
Doxygen breaks very often on mips64, and AFAICT
On Tue Sep 20, 2016 at 01:33:34AM +0100, Stuart Henderson wrote:
> These plist changes for every update are getting silly, I think I'd
> rather disable doxygen in those ports..
>
Other opinions or agreements?
>
>
> On 2016/09/19 21:38, Rafael Sadowski wrote:
> > Hi ports@
> >
> > updated
These plist changes for every update are getting silly, I think I'd
rather disable doxygen in those ports..
On 2016/09/19 21:38, Rafael Sadowski wrote:
> Hi ports@
>
> updated again. Doxygen port changes:
>
> - Switch to qt5
> -- Build doxyapp, doxyindexer applications (Tested @amd64)
> -
Hi ports@
updated again. Doxygen port changes:
- Switch to qt5
-- Build doxyapp, doxyindexer applications (Tested @amd64)
- Some patches are no longer needed (committed upstream)
- Take Maintainer
I checked all ports with doxygen usage:
devel/libmtpREVISION bump and updated
On Thu Dec 10, 2015 at 10:24:35PM +, Stuart Henderson wrote:
> On 2015/12/10 22:39, Rafael Sadowski wrote:
> > On Thu Dec 10, 2015 at 10:01:46AM +, Stuart Henderson wrote:
> > > On 2015/12/09 19:09, Jérémie Courrèges-Anglas wrote:
> > > > >> - Don't use own libmd5 but base md5
> > > > >> -
Hi,
Stuart Henderson writes:
> On 2015/12/10 22:39, Rafael Sadowski wrote:
>> On Thu Dec 10, 2015 at 10:01:46AM +, Stuart Henderson wrote:
>> > On 2015/12/09 19:09, Jérémie Courrèges-Anglas wrote:
>> > > >> - Don't use own libmd5 but base md5
>> > > >> - Use MD5Data()
On 2015/12/09 19:09, Jérémie Courrèges-Anglas wrote:
> >> - Don't use own libmd5 but base md5
> >> - Use MD5Data() instead of MD5Buffer+MD5SigToString
>
> What is the point with those two items? This adds clutter to this
> update and possible problems for the following ones.
These changes are
On 2015/12/10 22:39, Rafael Sadowski wrote:
> On Thu Dec 10, 2015 at 10:01:46AM +, Stuart Henderson wrote:
> > On 2015/12/09 19:09, Jérémie Courrèges-Anglas wrote:
> > > >> - Don't use own libmd5 but base md5
> > > >> - Use MD5Data() instead of MD5Buffer+MD5SigToString
> > >
> > > What is the
On Thu Dec 10, 2015 at 10:01:46AM +, Stuart Henderson wrote:
> On 2015/12/09 19:09, Jérémie Courrèges-Anglas wrote:
> > >> - Don't use own libmd5 but base md5
> > >> - Use MD5Data() instead of MD5Buffer+MD5SigToString
> >
> > What is the point with those two items? This adds clutter to this
Stuart Henderson writes:
> On 2015/12/09 19:09, Jérémie Courrèges-Anglas wrote:
>> >> - Don't use own libmd5 but base md5
>> >> - Use MD5Data() instead of MD5Buffer+MD5SigToString
>>
>> What is the point with those two items? This adds clutter to this
>> update and possible
Rafael Sadowski writes:
> Hi @ports,
Hi Rafael,
> nobody cares *ping* harder ;-)
This is the correct method indeed. :)
> Cheers, Rafael
>
> On Sun Nov 22, 2015 at 04:51:14PM +0100, Rafael Sadowski wrote:
>> Hi ports@
>>
>> after my first attempt here is the new diff
Hi @ports,
nobody cares *ping* harder ;-)
Cheers, Rafael
On Sun Nov 22, 2015 at 04:51:14PM +0100, Rafael Sadowski wrote:
> Hi ports@
>
> after my first attempt here is the new diff to update doxygen.
>
> doxygen port highlights:
>
> - switch to CMake
> - Don't use own libmd5 but base md5
> -
On Sun Nov 22, 2015 at 04:51:14PM +0100, Rafael Sadowski wrote:
> Hi ports@
>
> after my first attempt here is the new diff to update doxygen.
>
> doxygen port highlights:
>
> - switch to CMake
> - Don't use own libmd5 but base md5
> - Use MD5Data() instead of MD5Buffer+MD5SigToString
>
> I
Hi ports@
after my first attempt here is the new diff to update doxygen.
doxygen port highlights:
- switch to CMake
- Don't use own libmd5 but base md5
- Use MD5Data() instead of MD5Buffer+MD5SigToString
I checked all ports with doxygen usage.
- No changes with 1.8.10:
audio/liblo
27 matches
Mail list logo