shment, I'd
recommend the Gobo devs take a look at it.
There is also this comment on the Limba post:
Jasem Mutlaq commented on 29. January 2015:
[Limba has a] Refreshing approach, but with all the work done in Nix
and Lennart’s proposal, I think mos
t;Invalid
signature - you appear to be using an old version of
Compile/Scripts.)" and any appropriate solution(s), whatever it/they
may be.
-mpb
___
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
g recipes for each version of Compile and
Scripts so that specific versions can be reliably Compiled? I worry
that if I use the current SVN-based recipes, I will be installing
potentially buggy development snapshots.
-mpb
___
gobolinux-devel mailing lis
mpile. Perhaps it should?
Thanks!
-mpb
___
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
e to do what they want (including not releasing
modified source code, as in the BSD or better yet, Public Domain),
or...
3) Neither (in the case of closed source, copyrighted, proprietary software).
That said, I take no position on what license Gobo should use.
-mpb
___
#Installation
Thanks!
mpb
___
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
we discussed before, I have been thinking about
expanding recipes.gobolinux.org to include specific information about
current Recipe and Package versions (including across the various
repos), but I have been too busy to implement anything. I have one
more week of being-very-busy, and the
tem/Links/Headers ${CPPFLAGS}"
2 and 3 are already done in System/Settings/bashrc - assuming you
Compile bash inside Rootless. If you do not Compile bash, then these
settings will fall through the cracks in Rootless.
In the past I have advocated for similar additions to StartRootless
ell go back and clean up the recipe
viewer so that it is getting all its information from the proper
authoritative sources.
Also, can someone please explain what System/Index is? There has been
some discussion of it recently, but I have not been able to figure out
what it is/does.
nd/or the Gobo toolchain) so they ever
require root access. Optional use of sudo is fine.
(When applications require special user accounts, I typically create
those accounts manually. Then I run Rootless inside that account to
install Asterisk, Postfix, Ap
On Jan 2, 2008 1:50 AM, Carlo Calica <[EMAIL PROTECTED]> wrote:
> Hot on the heels of the 014 LiveCD release, I'd like to announce the
> 014 LiveFlash release.
Very nice! I wish Ubuntu would do this, too.
-mpb
___
gobolinux-d
ningful: if there is a symlink to a directory (as opposed
to complete expansion) you know that only one program provides that
directory.
-mpb
___
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
ource for recipes.gobolinux.org.
-mpb
___
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
aries provided by the host system via the pkg-config mechanism of
library detection.
Thanks!
-mpb
___
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
more willing to monitor the wiki if some anti-spam barrier
(such as reCAPTCHA) were in place.
-mpb
___
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
untProgram GCC 4.1.2".
Both are just as easy to remember and use. "UseProgram" saves you the
bother of having to mess with chroots.
-mpb
___
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
mply:
export PATH=$PATH:$goboPrefix/Programs/GCC/4.1.2/bin
By changing PATH, you can choose which version of GCC will be used.
Similar result without using chroot at all.
-mpb
___
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
r apt-get or Compile. The primary motivation
behind my proposal was the desire for the introduction of Required vs.
Optional Dependencies, especially for use with Rootless, so that I
could quickly and reliably skip Optional Dependencies. All the rest
was just imagining one po
d up compiling PHP by hand. With GoboRootless, I
simply store store my PHP configure args in a Makefile that calls
Compile, which is a much nicer solution.
-mpb
___
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
t; recipe. You'd have to manually
update the /bin/sh symlink.
For reference, I've filed a bug report regarding problems with Scripts+dash.
http://bugs.gobolinux.org/view.php?id=118
-mpb
___
gobolinux-devel mailing list
gobolinux-devel@lists.gobol
Compile on Rootless. This is not a big deal for me, but it would be
nice if Rootless would work regardless of what /bin/sh is.
Below is a transcript of what happens when I try to "Compile wget"
when /bin/sh -> dash.
-mpb
[EMAIL PROTECTED] ~]Compile wget
Compile: Locating a re
Hi,
Attached is an AutoPatch script that does everything I want.
AutoPatch will make a backup copy of to
.ap-orig and then Edit the file.
AutoPatch will recursively descend running diff
for every .ap-orig it finds.
-mpb
AutoPatch
Description: Binary data
does this? I thought
I would ask before re-inventing the wheel.
The problem with 'diff -Naur dir.orig dir' is that extra work is
required because:
(a) it requires two directories and
(b) it reports the backup (*~) files that emacs leaves behind as changes.
Tha
@")
>
> Should we add the lua files? or let then without it?.
Are you using Lua 5.0 or 5.1?
I believe that in Lua 5.1, modules do not require .lua wrappers - the
.so files can be directly required.
Do we want to support both Lua 5.1 and 5.0, or just 5.1?
Supporting both may be more com
d
like to synchronize the locations that are used.
Thanks!
-mpb
___
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
o (perhaps optionally) include
support for GDC.
The GDC installation instructions are here:
http://dgcc.sourceforge.net/gdc/install.html
More information on GDC and the D Programming Language is here:
http://dgcc.sourceforge.net/
http://digitalmars.com/d/
Tha
these
pages, the browser would time-out. I suspect a bug/infinite loop in
MediaWiki, but have not yet taken the time to track down the problem.
Step 17) Automate the review process with a PHP "macro" script.
Reviewing pages will then be an automated 2 click per page process.
---
age last patrolled by" feature,
but I'm not sure how extensive it is, or if it is suitable here. It
may just be an anti-vandalism feature.
I want to know: who, when and optionally at what software version the
page was last reviewed.
t; Step 6) Write and enforce WikiTeam policy guidlines.
> >
> > Step 7) Implement maintenence tracking techniques
> > Each page in the wiki will link to the appropriate "Last_Reviewed_..."
> > page.
> >
> > For example:
> >
> > This page [[La
Step 7) Implement maintenence tracking techniques
In the Community->WikiTeam->Mainetance category, create the following
pages:
Last_Reviewed__
Each page in the wiki will link to the appropriate "Last_Reviewed_..."
page.
For example:
This page [[Last Reviewed March 2007]] by mp
. So,
> we need both.
Is Linux-Libc-Headers obsolete? Deprecated?
http://gobo.dreamhosters.com/recipes/?name=headers&search=Recipes
Glibc does appear to depend on Linux-Headers and not Linux-Libc-Headers
http://gobo.dreamhosters.com/recipes/?list=Glibc&ver=2.5-r3&am
31 matches
Mail list logo