special category for haskell ports

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

special category for haskell ports

Matthias Kilian
<kili_p> can i add category 'bullshit' to all haskell ports?
<tobiasu_p> only if you port systemd and put it there

So I ported systemd from http://hackage.haskell.org/package/systemd
(proof attached, and please note how careful I copied the blurb
from upstreams github project into pkg/DESCR). I'm not going to
commit *that* one, but, well, I ported it ;-)

Ok to commit the innocent bits below to lang/ghc?

Index: Makefile
===================================================================
RCS file: /cvs/ports/lang/ghc/Makefile,v
retrieving revision 1.110
diff -u -p -r1.110 Makefile
--- Makefile 22 Nov 2014 20:23:22 -0000 1.110
+++ Makefile 15 Dec 2014 22:48:11 -0000
@@ -14,7 +14,7 @@ COMMENT-doc = documentation for GHC
 DISTNAME = ghc-${MODGHC_VER}
 PKGNAME-main = ghc-${MODGHC_VER}
 PKGNAME-doc = ghc-doc-${MODGHC_VER}
-CATEGORIES = lang devel
+CATEGORIES = lang devel bullshit
 HOMEPAGE = http://www.haskell.org/ghc/
 
 # Version of the precompiled binaries
Index: ghc.port.mk
===================================================================
RCS file: /cvs/ports/lang/ghc/ghc.port.mk,v
retrieving revision 1.34
diff -u -p -r1.34 ghc.port.mk
--- ghc.port.mk 22 Nov 2014 20:23:22 -0000 1.34
+++ ghc.port.mk 15 Dec 2014 22:48:11 -0000
@@ -35,7 +35,7 @@ MODGHC_BUILD ?=
 . if !${MODGHC_BUILD:L:Mnort}
 PKGNAME ?= hs-${DISTNAME}
 RUN_DEPENDS += lang/ghc=${MODGHC_VER}
-CATEGORIES += lang/ghc
+CATEGORIES += lang/ghc bullshit
 . endif
 
 . if ${MODGHC_BUILD:L:Mhackage}

hs-systemd.tgz (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: special category for haskell ports

Ian McWilliam-2
On 16/12/2014 9:57 AM, Matthias Kilian wrote:
> <kili_p> can i add category 'bullshit' to all haskell ports?
>

Can we just have a category 'bullshit' and move samba there. Please,
pretty please.

* BUG 10472: Revert buildtools/wafadmin/Tools/perl.py back to upstream
       state.

https://git.samba.org/?p=samba.git;a=log;h=21764ef2249447cf480044486d6537ffbca6063d

"pidl/wscript: remove --with-perl-* options

These are not needed anymore as we have useful defaults now"

Guess what those defaults are.......and they don't even come close to valid perl
data, lib or site perl directories.........

Ian McWilliam


Reply | Threaded
Open this post in threaded view
|

samba, perl and vendorarch etc [Re: special category for haskell ports]

Stuart Henderson-6
On 2014/12/16 21:23, Ian McWilliam wrote:
> * BUG 10472: Revert buildtools/wafadmin/Tools/perl.py back to upstream
>       state.

With the next line too, this is
"We are reverting buildtools/wafadmin/Tools/perl.py back to upstream state.
Everything special is now in buildtools/wafsamba/samba_perl.py."

This looks like they are trying to move back to standard waf where possible
though, keeping samba-specific bits in separate files, surely that's a good thing..?

> https://git.samba.org/?p=samba.git;a=log;h=21764ef2249447cf480044486d6537ffbca6063d
>
> "pidl/wscript: remove --with-perl-* options
>
> These are not needed anymore as we have useful defaults now"
>
> Guess what those defaults are.......and they don't even come close to valid perl
> data, lib or site perl directories.........

https://git.samba.org/?p=samba.git;a=blob;f=buildtools/wafsamba/samba_perl.py;h=3909aba2ee47e5134c1609a385d26f1aa1e49b6b;hb=21764ef2249447cf480044486d6537ffbca6063d

This uses Config(3p) to fetch some directories, but we aren't setting
them e.g.

$ perl -V:vendorprefix -V:vendorarch -V:vendorlib
vendorprefix='';
vendorarch='';
vendorlib='';

Should we be?

Reply | Threaded
Open this post in threaded view
|

Re: samba, perl and vendorarch etc [Re: special category for haskell ports]

Ian McWilliam-2
On 17/12/2014 12:47 AM, Stuart Henderson wrote:
> On 2014/12/16 21:23, Ian McWilliam wrote:
>> * BUG 10472: Revert buildtools/wafadmin/Tools/perl.py back to upstream
>>        state.
> With the next line too, this is
> "We are reverting buildtools/wafadmin/Tools/perl.py back to upstream state.
> Everything special is now in buildtools/wafsamba/samba_perl.py."
>
> This looks like they are trying to move back to standard waf where possible
> though, keeping samba-specific bits in separate files, surely that's a good thing..?

Yeah if they took upstream holus bolus and not just piecemeal. Those
billions of waf patches still apply.........

>> https://git.samba.org/?p=samba.git;a=log;h=21764ef2249447cf480044486d6537ffbca6063d
>>
>> "pidl/wscript: remove --with-perl-* options
>>
>> These are not needed anymore as we have useful defaults now"
>>
>> Guess what those defaults are.......and they don't even come close to valid perl
>> data, lib or site perl directories.........
> https://git.samba.org/?p=samba.git;a=blob;f=buildtools/wafsamba/samba_perl.py;h=3909aba2ee47e5134c1609a385d26f1aa1e49b6b;hb=21764ef2249447cf480044486d6537ffbca6063d
>
> This uses Config(3p) to fetch some directories, but we aren't setting
> them e.g.
>
> $ perl -V:vendorprefix -V:vendorarch -V:vendorlib
> vendorprefix='';
> vendorarch='';
> vendorlib='';
>
> Should we be?
>
>
Something needs to or it's more waf patching.

Ian McWilliam