>with that symlink, both
>
> man $PACKAGE_NAME i.e. man linuxbrew-wrapper
> man $WRAPPER_NAME i.e. man linuxbrew
>
>work.
sure, I just got confused between linuxbrew and brew :)
>Oops, that's a typo, in fact I mean the 'x' mode, not 'r'.
>After all how can the ruby interpreter interpr
Hi,
On Tue, 2015-08-25 at 16:29 +, Gianfranco Costamagna wrote:
> yes I got confused by this line
> usr/share/man/man7/linuxbrew-wrapper.7.gz usr/share/man/man7/linuxbrew.7.gz
with that symlink, both
man $PACKAGE_NAME i.e. man linuxbrew-wrapper
man $WRAPPER_NAME i.e. man linuxbre
Hi,
>Oops...Sorry for that...
>By mistake I introduced this bug into the wrapper script.
>Patch [1] fixes this bug. And it was fixed in the freshly uploaded
>mentor package.
wonderful
>Please note that, the linuxbrew installer will pull a manpage of brew
>(as above /home/lumin/.linuxbrew/share
On Tue, 2015-08-25 at 09:54 +, Gianfranco Costamagna wrote:
> 1) I did a build&install of the package, and I can't make it work
>
>
>
> brew install cmake
> brew
> brew --help
> linuxbrew --help
>
> returns nothing
Oops...Sorry for that...
By mistake I introduced this bug into the wrapper
Hi Lumin,
the packaging now is really fine for me, I'm going to sponsor soonish.
1) I did a build&install of the package, and I can't make it work
brew install cmake
brew
brew --help
linuxbrew --help
returns nothing
2) man brew doesn't work, man linuxbrew works
3) looking at the source,
Hi Gianfranco Costamagna,
On Wed, 2015-08-19 at 13:07 +, Gianfranco Costamagna wrote:
> BTW the git urls are wrong:
>
> examples of good git urls:
>
> Vcs-Git: git://anonscm.debian.org/collab-maint/package-xx.git
> Vcs-Browser: http://anonscm.debian.org/cgit/collab-maint/package-xx.git
Fixe
Hi Lumin,
>I have just uploaded a updated package to mentors several seconds ago,
>and I will CC you later in the d-devel discussion.
thanks but I already follow -devel :)
>If I don't write them in dch, even I will forget what I've done to
>the package months later.
>
>Policy chapter 4.4 said
Hi Gianfranco Costamagna,
I have just uploaded a updated package to mentors several seconds ago,
and I will CC you later in the d-devel discussion.
On Tue, 2015-08-18 at 08:09 +, Gianfranco Costamagna wrote:
> d/changelog should mention only initial release (closes: #) and nothing
> more
Hi Lumin,
some new stuff
(btw feel free to discuss on -devel, there is no need to have a perfect package
for the discussion)
d/changelog should mention only initial release (closes: #) and nothing
more.
debian/linuxbrew-wrapper.lintian-overrides
useless now?
debian/copyright, please rethi
Hi Lumin,
>I didn't mean "overriding the env is bad". I mean:
>-> can we directly add ENVs for users?
> -> how about doing this in wrapper script:
> sed -i -e "$a\$(cat /usr/share/.../example/profile)" .bashrc
> -> very bad.
>Then can ENVs be handled automatically?
>
>Then there are 2 th
Hi Gianfranco Costamagna,
On Mon, 2015-08-17 at 08:27 +, Gianfranco Costamagna wrote:
> yes, exactly the point I had, so somewhere the user should be aware that
> reporting
> the bug on Debian Bug Tracking System is *wrong*.
> and here we are:
> how do you say that to the user?
> You say ove
Hi Lumin
>Such "packaging bug" is upstream bug, and is handled by Homebrew
>and Linuxbrew upstream. And files made that trouble was not provided
>by Debian package ..
yes, exactly the point I had, so somewhere the user should be aware that
reporting
the bug on Debian Bug Tracking System i
Hi Gianfranco Costamagna,
On Sun, 2015-08-16 at 07:26 +, Gianfranco Costamagna wrote:
> yes, this is not a problem, and this is already done locally (manually) by
> many
> folks.
>
> But who will take care of "packaging bug x for package y installed with
> linuxbrew?"
Such "packaging bug"
Hi Lumin,
>
>Well... not going to bring trouble to apt/dpkg.
>
>Since linuxbrew is by default a home-based pacakge management tool,
>it is useful e.g when a group of people are working on the same
>amd64 workstation and some of them have no root/sudo access.
>In that circumstance, one can conven
Hi Gianfranco Costamagna,
On Thu, 2015-08-13 at 11:53 +, Gianfranco Costamagna wrote:
> General Note: I don't think I'll sponsor this package without a discussion on
> debian-devel mail list,
>
> because I do not honestly think we need another package management, specially
> because
> mixi
Hi Zhou,
General Note: I don't think I'll sponsor this package without a discussion on
debian-devel mail list,
because I do not honestly think we need another package management, specially
because
mixing stuff might lead to libraries incompatibilities, and something more.
Do you install so
Hi mentors,
Weeks ago I intended to package linuxbrew,
the missing package manager, which is a fork of Homebrew (Mac OS X).
Linuxbrew it's Formula update is managed by git,
hence initially I found it tricky to manage original linuxbrew
with gbp tools, for these reason:
* if original linuxbrew (
17 matches
Mail list logo
