Re: [wmii] Gentoo

2009-05-05 Thread KIMURA Masaru
Hi,

2009/5/6 Robert C Corsaro :
[SNIP]
> KIMURA,
>
> Sounds good.  I'll probably change a few things while I'm at it.  Any reason
> you use $package-hg instead of $package-?  I'm just wondering as I've
> always used  to indicate tip in my ebuilds.

There is no technical reason why I use $package-hg instead of
$package. I'd just label what scm tool is used by the upstream.

The reason why I don't use  as ebuild version number is to note hg
revision when I updated for myself.
And IIRC, the file, DISTRIBUTORS said something like "package should
tag hg revision as packaged wmii's version number."

[SNIP]



Re: [wmii] Gentoo

2009-05-05 Thread Kris Maglione

On Tue, May 05, 2009 at 09:46:47PM -0400, Robert C Corsaro wrote:

Kris,

* I notice in the official ebuild, and KIMURA's ebuild there is some sed  
hacking of config.mk.  Does it make sence to just package a  
config.local.mk with the ebuild, or is there some reason why sed hacking  
is better?


No, it should stick to config.local.mk; I have an arch PKGBUILD 
that should serve as an example. I'll commit it tomorrow.


* Can I safely assume that dmenu tip and libixp tip will be dependencies  
for wmii tip?  Are there any others?


No, there's no need for dmenu. libixp-hg is a build dep, yes.

* I can, as KIMURA suggested, make this a suckless overlay.  This might  
warrent having it's own repo on suckless.  I'll already be including  
ebuilds for dmenu and libixp.  I don't know if I'll get around to making  
ebuilds for all suckless packages, but it's a good starting point if  
someone else comes along with some more.  What do you think?


I think a suckless overlay would be a good idea, but you should 
talk to Anselm ([email protected]) about it. I'm sure that others 
would be willing to maintain ebuilds for most of the other 
suckless software.


--
Kris Maglione

If you think your management doesn't know what it's doing or that your
organisation turns out low-quality software crap that embarrasses you,
then leave.
--Edward Yourdon




Re: [wmii] Gentoo

2009-05-05 Thread Robert C Corsaro

KIMURA Masaru wrote:

Hi,

2009/5/6 Robert C Corsaro :
  

KIMURA Masaru wrote:


Hi,

2009/5/6 Robert C Corsaro :

  

Does anyone maintain a portage overlay for tip wmii?



[SNIP]

http://dev.gentoo.gr.jp/~hiyuh/cgi-bin/hgweb.cgi/file/tip/x11-wm/wmii-hg


  

Ah, great, thank you. �If you need anything done, like moving it to the
googlecode mirror, I can help.



This wmii's ebuild is just for one of my miscellaneous overlay that
doesn't come from as gentoo's official ones. If you'd like to maintain
only wmii related apps (or, suckless.org apps?), you can copy to fork
w/o my blame.

If Kris encourages to share this ebuilds under code.suckless.org or
wmii.googlecode.com, I have no objection to separate that ebuilds from
my other craps.
  

KIMURA,

Sounds good.  I'll probably change a few things while I'm at it.  Any 
reason you use $package-hg instead of $package-?  I'm just wondering 
as I've always used  to indicate tip in my ebuilds.


Kris,

* I notice in the official ebuild, and KIMURA's ebuild there is some sed 
hacking of config.mk.  Does it make sence to just package a 
config.local.mk with the ebuild, or is there some reason why sed hacking 
is better?


* Can I safely assume that dmenu tip and libixp tip will be dependencies 
for wmii tip?  Are there any others?


* I can, as KIMURA suggested, make this a suckless overlay.  This might 
warrent having it's own repo on suckless.  I'll already be including 
ebuilds for dmenu and libixp.  I don't know if I'll get around to making 
ebuilds for all suckless packages, but it's a good starting point if 
someone else comes along with some more.  What do you think?





Re: [wmii] Gentoo

2009-05-05 Thread KIMURA Masaru
Hi,

2009/5/6 Robert C Corsaro :
> KIMURA Masaru wrote:
>>
>> Hi,
>>
>> 2009/5/6 Robert C Corsaro :
>>
>>>
>>> Does anyone maintain a portage overlay for tip wmii?
>>>
>>
>> [SNIP]
>>
>> http://dev.gentoo.gr.jp/~hiyuh/cgi-bin/hgweb.cgi/file/tip/x11-wm/wmii-hg
>>
>>
>
> Ah, great, thank you.  If you need anything done, like moving it to the
> googlecode mirror, I can help.

This wmii's ebuild is just for one of my miscellaneous overlay that
doesn't come from as gentoo's official ones. If you'd like to maintain
only wmii related apps (or, suckless.org apps?), you can copy to fork
w/o my blame.

If Kris encourages to share this ebuilds under code.suckless.org or
wmii.googlecode.com, I have no objection to separate that ebuilds from
my other craps.



Re: [wmii] Gentoo

2009-05-05 Thread Robert C Corsaro

KIMURA Masaru wrote:

Hi,

2009/5/6 Robert C Corsaro :
  

Does anyone maintain a portage overlay for tip wmii?


[SNIP]

http://dev.gentoo.gr.jp/~hiyuh/cgi-bin/hgweb.cgi/file/tip/x11-wm/wmii-hg

  
Ah, great, thank you.  If you need anything done, like moving it to the 
googlecode mirror, I can help.




Re: [wmii] Gentoo

2009-05-05 Thread KIMURA Masaru
Hi,

2009/5/6 Robert C Corsaro :
> Does anyone maintain a portage overlay for tip wmii?
[SNIP]

http://dev.gentoo.gr.jp/~hiyuh/cgi-bin/hgweb.cgi/file/tip/x11-wm/wmii-hg



Re: [wmii] Gentoo

2009-05-05 Thread Robert C Corsaro

Kris Maglione wrote:

On Tue, May 05, 2009 at 07:41:13PM -0400, Robert C Corsaro wrote:
  
Gentoo uses ebuilds, which are just a layer above make.  The ebuild  
basically downloads the source, compiles and installs.  An overlay is  
just a set of ebuilds that aren't in the official gentoo repository.   
When you emerge (install) a package, it looks in any overlays you have  
first, and then in the official portage tree(set of ebuilds). There is 
also a program called layman which manages overlays for users.  It 
requires a layman-list.xml file somewhere on the web to tell it  
where/how to get the overlay(s).  I'll create this too.  The only  
requirement is that the layman-list.xml can be accessed by http url, and  
that the overlay can be accessed via tar(http url), rsync, hg, svn, git  
or bzr.


I'd love to leave it in your repo, one less headache for me.



Ok, I can give you commit access to the Google Code mirror of 
the repo, and you can maintain the overlay there. I'd suggest 
using /pkg/gentoo, which will be accessible at:


 http://wmii.googlecode.com/hg/pkg/gentoo/

If that's acceptable, please send the required changes (commit 
them to your private repo and use "hg export"), and I'll add you 
to the Google Code project.


  
Ok, we'll try that.  The only worry I have is that for layman to work, 
the checkout has to have the directory structure in the root.  It looks 
like hg clone http://wmii.googlecode.com/hg/pkg/gentoo/ doesn't checkout 
the subdir, but the entire repo.  Can that subdir be packaged as a tar 
somewhere?  Anyway, we'll figure something out.




Re: [wmii] Gentoo

2009-05-05 Thread Kris Maglione

On Tue, May 05, 2009 at 07:41:13PM -0400, Robert C Corsaro wrote:
Gentoo uses ebuilds, which are just a layer above make.  The ebuild  
basically downloads the source, compiles and installs.  An overlay is  
just a set of ebuilds that aren't in the official gentoo repository.   
When you emerge (install) a package, it looks in any overlays you have  
first, and then in the official portage tree(set of ebuilds). There is 
also a program called layman which manages overlays for users.  It 
requires a layman-list.xml file somewhere on the web to tell it  
where/how to get the overlay(s).  I'll create this too.  The only  
requirement is that the layman-list.xml can be accessed by http url, and  
that the overlay can be accessed via tar(http url), rsync, hg, svn, git  
or bzr.


I'd love to leave it in your repo, one less headache for me.


Ok, I can give you commit access to the Google Code mirror of 
the repo, and you can maintain the overlay there. I'd suggest 
using /pkg/gentoo, which will be accessible at:


http://wmii.googlecode.com/hg/pkg/gentoo/

If that's acceptable, please send the required changes (commit 
them to your private repo and use "hg export"), and I'll add you 
to the Google Code project.


--
Kris Maglione

TeX has found at least one bug in every Pascal compiler it's been run
on, I think, and at least two in every C compiler.
--Donald Knuth




Re: [wmii] Gentoo

2009-05-05 Thread Robert C Corsaro

Kris Maglione wrote:

On Tue, May 05, 2009 at 07:22:32PM -0400, Robert C Corsaro wrote:
  
Does anyone maintain a portage overlay for tip wmii?  If not, I could.   
I could host it on my person host, or you can give me a repo that I can  
check files into, that can be downloaded via http.



Not that I know of. How do portage overlays work? I can probably 
give you commit access if it can be done inside of wmii's repo. 
I'd prefer to officially host packages for the major distros 
where possible.


  
Gentoo uses ebuilds, which are just a layer above make.  The ebuild 
basically downloads the source, compiles and installs.  An overlay is 
just a set of ebuilds that aren't in the official gentoo repository.  
When you emerge (install) a package, it looks in any overlays you have 
first, and then in the official portage tree(set of ebuilds). 
There is also a program called layman which manages overlays for users.  
It requires a layman-list.xml file somewhere on the web to tell it 
where/how to get the overlay(s).  I'll create this too.  The only 
requirement is that the layman-list.xml can be accessed by http url, and 
that the overlay can be accessed via tar(http url), rsync, hg, svn, git 
or bzr.


I'd love to leave it in your repo, one less headache for me.





Re: [wmii] Gentoo

2009-05-05 Thread Kris Maglione

On Tue, May 05, 2009 at 07:22:32PM -0400, Robert C Corsaro wrote:
Does anyone maintain a portage overlay for tip wmii?  If not, I could.   
I could host it on my person host, or you can give me a repo that I can  
check files into, that can be downloaded via http.


Not that I know of. How do portage overlays work? I can probably 
give you commit access if it can be done inside of wmii's repo. 
I'd prefer to officially host packages for the major distros 
where possible.


--
Kris Maglione

The X server has to be the biggest program I've ever seen that doesn't
do anything for you.
--Ken Thompson