being slack, subverting the
Debian system, or is Debian guilty too?
--
John Skaller skaller at users dot sourceforge dot net
Async PL, Realtime software consultants
Checkout Felix: http://felix.sourceforge.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble
if you want, as a convenience.
Just put it in a directory 'initial-packaging' or
something. Then you can make the debian package
by just copying it .. and you can still patch
that copy without changing the tarball.
Next release -- get the initial-packaging right!
--
John Skaller skaller at users
On Tue, 2006-02-28 at 19:18 +0200, Panu Kalliokoski wrote:
On Wed, Mar 01, 2006 at 03:52:04AM +1100, skaller wrote:
It's your call, but since making them non-native is not really that much
more work, I'd recommend doing it that way.
However there is a reason, it is political
code. The system knows when sources change
and rebuilds automatically. The generated binaries are
an implementation detail.
Clearly you have different needs and requirements for
your translator.
BTW: can I have a look?
--
John Skaller skaller at users dot sf dot net
Felix, successor to C++: http
upstream developers.
--
John Skaller skaller at users dot sf dot net
Felix, successor to C++: http://felix.sf.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
. Requires a design committee and
development team (I'm a programmer not a politician)
Any advice, comments, hints, ideas or offers to write
the new tool appreciated!
--
John Skaller skaller at users dot sf dot net
Felix, successor to C++: http://felix.sf.net
--
To UNSUBSCRIBE, email to [EMAIL
On Mon, 2006-01-30 at 15:20 +1100, skaller wrote:
Hi, I need some advice on the following problem.
* it generates redundant and possibly incorrect lists of
libraries for systems running Elf dynamic linkers,
which know how to find closure of shared library
dependencies correctly
and build it from source, build an rpm package or build a deb package. I
sent
This is the way RPM works, but not Debian. Tell him no user will
ever build the deb package because it is *in* Debian.
Some old version of it is anyhow :)
--
John Skaller skaller at users dot sf dot net
Felix
On Fri, 2005-12-30 at 07:45 +, Neil Williams wrote:
On Friday 30 December 2005 7:11 am, skaller wrote:
Until the NM backlog is cleared, I'd recommend applying now if you see any
prospect of this changing in the next year. It could be at least 8 months
before you get assigned
On Fri, 2005-12-30 at 09:46 +0100, Frank Küster wrote:
skaller [EMAIL PROTECTED] wrote:
If your upstream software has a good installation procedure - something
like the autotools
[Lol .. you really don't want to hear my opinion of autotools :]
type with the possibility to change directory
On Wed, 2005-12-28 at 23:06 -0800, Russ Allbery wrote:
skaller [EMAIL PROTECTED] writes:
This is frustrating but it's hard to really do anything about this since
neither Ubuntu nor Debian is really able to sync development cycles with
the other.
Sure they are. The question is if the teams
a bit more and to make it
a bit easier for more people to get involved.
--
John Skaller skaller at users dot sf dot net
Felix, successor to C++: http://felix.sf.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
and quite
discouraging for those wishing to contribute software but NOT
wishing to become full time Debian developers -- and that a
good deal more work might be done if it was easier for THOSE
people to contribute more directly.
--
John Skaller skaller at users dot sf dot net
Felix, successor to C
On Thu, 2005-12-29 at 09:28 -0800, Richard A. Hecker wrote:
skaller wrote:
I can suggest whole heap of things that would improve
the situation .. but I can't choose which ones to
implement. All I can do is ask .. please do SOMETHING
to streamline the process a bit more and to make it
a bit
On Thu, 2005-12-29 at 17:14 -0200, Guilherme de S. Pastore wrote:
Em Sex, 2005-12-30 às 05:08 +1100, skaller escreveu:
I'm an outsider, I'm giving my impression of the process
to insiders that cannot see what I do from the outside
(as both a user and software developer).
Do not forget
to be a generalist as well as probably
specialising in some packaging niche.
--
John Skaller skaller at users dot sf dot net
Felix, successor to C++: http://felix.sf.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
would never bother
to do any serious work that way. Committing directly is the
only effective way.
--
John Skaller skaller at users dot sf dot net
Felix, successor to C++: http://felix.sf.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
On Wed, 2005-12-28 at 21:27 -0200, Gustavo Franco wrote:
skaller wrote:
On Wed, 2005-12-28 at 13:37 -0200, Gustavo Franco wrote:
it's
just a matter to publish the patches (a good PQM will do that for you)
and let the others branch' maintainers do the merge when necessary
on a modification .. but I personally
find a couple of seconds is more productive. Ok, I exaggerate
a little (I'm as well known for that as Debian is for being
conservative and sluggish :).
--
John Skaller skaller at users dot sf dot net
Felix, successor to C++: http://felix.sf.net
.
--
John Skaller skaller at users dot sf dot net
Felix, successor to C++: http://felix.sf.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
might even say 'complement' implies
completion, whereas 'supplement' implies enrichment.
In particular, complementing does not add anything
new conceptually, the complement was already implicit.
--
John Skaller skaller at users dot sf dot net
Felix, successor to C++: http://felix.sf.net
handling etc ..)?
--
John Skaller skaller at users dot sf dot net
Felix, successor to C++: http://felix.sf.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
that you actually
use it (and not just g++), and filing a bug on gcc-4.0.
It is worth retrying.
I sometimes get this error, and it goes away when I retry,
particularly after a reboot.
--
John Skaller skaller at users dot sf dot net
Felix, successor to C++: http://felix.sf.net
--
To UNSUBSCRIBE
-master.
So you have to do what they want .. even if it isn't
necessary, correct, or sensible.. :)
--
John Skaller skaller at users dot sourceforge dot net
signature.asc
Description: This is a digitally signed message part
detail.
IMHO: Every package should be independently useful: my rtl
isn't so it should not be *permitted* in a separate package.
[BTW: perhaps this will change in a future release]
--
John Skaller skaller at users dot sourceforge dot net
signature.asc
Description: This is a digitally signed
the wrong symbol.
(b) Even if the ABI is the same, the semantics may not be.
Current example: libstdc++ .. :)
--
John Skaller skaller at users dot sourceforge dot net
signature.asc
Description: This is a digitally signed message part
On Sat, 2005-09-03 at 23:13 -0700, Steve Langasek wrote:
On Sun, Sep 04, 2005 at 01:04:40AM +1000, skaller wrote:
On Sat, 2005-09-03 at 04:19 -0700, Steve Langasek wrote:
At the present time and given the current state of the software I
believe it is not in Debian's best interest
be handled if
all the symbols (both exported and imported) are versioned,
for example if A1.1.1 really did depend on C1.1, then you could
load both C1.1.1 and C1.2.1 .. ASSUMING the libraries are reentrant
(don't have static data).
Pls let me know if I got the argument correct ..?
--
John Skaller
On Sun, 2005-09-04 at 04:08 -0700, Steve Langasek wrote:
On Sun, Sep 04, 2005 at 08:06:07PM +1000, skaller wrote:
The second part,
MIT_KRB5_17 {
global:
*;
}
specifies a symbol version to apply to all other exported symbols.
What is the effect of applying a symbol version
it is. However a policy could
be made and be enforced.
In particular, at present, pkg-config is plain useless
because it isn't consistently supported.
--
John Skaller skaller at users dot sourceforge dot net
signature.asc
Description: This is a digitally signed message part
upgrade to a new tarball/package -- and perhaps not even
the one in question, but one of its dependencies.
This problem would just go away if pkg-config we supported
properly, or a new system developed that was.
I don't know the answer, just the problem .. :)
--
John Skaller skaller at users dot
this is?
It does seem 'contrary' in some way to Debian's policy
of things going in particular places .. yet people don't
always actually put them there .. :)
--
John Skaller skaller at users dot sourceforge dot net
signature.asc
Description: This is a digitally signed message part
useless unless it is properly supported.
It's also not a very good program -- perhaps Debian can come
up with something better?
--
John Skaller skaller at users dot sourceforge dot net
signature.asc
Description: This is a digitally signed message part
On Fri, 2005-09-02 at 20:09 -0700, Steve Langasek wrote:
On Sat, Sep 03, 2005 at 12:46:31PM +1000, skaller wrote:
Does Debian have a policy on use of pkg-config?
On my Ubuntu systems there are some *.pc files, but the set
is not only incomplete .. it isn't closed either.
Perhaps pkg
On Thu, 2005-08-18 at 09:19 +0200, Bastian Venthur wrote:
This site is still not viewable with firefox.
I can see it fine.
--
John Skaller skaller at users dot sourceforge dot net
signature.asc
Description: This is a digitally signed message part
software is
also non-free IMHO :)
--
John Skaller skaller at users dot sourceforge dot net
signature.asc
Description: This is a digitally signed message part
shouldn't have. (There is a workaround:
you can rebuild everything any time you like).
--
John Skaller skaller at users dot sourceforge dot net
signature.asc
Description: This is a digitally signed message part
On Mon, 2005-08-01 at 23:18 +0200, FERREIRA Yohann wrote:
Hi all,
I am, by this mail, willing to become the debian maintainer of the guichan
library set.
What is Guichan?
Where is the site with the docs?
--
John Skaller skaller at users dot sourceforge dot net
signature.asc
, because
Package: A
Conflicts: B
really means B must be installed before A,
rather than what the word suggests to me,
namely, mutual exclusion.
--
John Skaller skaller at users dot sourceforge dot net
signature.asc
Description: This is a digitally signed message part
On Sat, 2005-07-30 at 08:55 -0700, Matt Brubeck wrote:
skaller wrote:
The problem is that you CAN install a package B which declares a
conflict with A, and then install A, which does not declare the
conflict. The conflict exists, nevertheless.
This isn't true. If B is installed and B
On Sun, 2005-07-31 at 01:39 +0200, Sven Mueller wrote:
skaller wrote on 30/07/2005 19:08:
On Sat, 2005-07-30 at 08:55 -0700, Matt Brubeck wrote:
You can test this yourself to see that it works correctly. For example,
try to install cfengine2 (Conflicts: cfengine) and then cfengine
is always physically installed
whenever you require a dependency, it is irrelevant
whether or not X or no-X is installed otherwise,
so the absence of one or the other is also irrelevant.
--
John Skaller skaller at users dot sourceforge dot net
signature.asc
Description: This is a digitally
not currently true, a no-X package should be created
by the package manager to prevent subsequent installation.
So it looks like 'no-X' is not simply needed to satisfy
an unusal request -- it is needed to repair a fundamental
bug in Debian.
--
John Skaller skaller at users dot sourceforge dot net
.
With just a .o object file, you'd need an additional
support library (and another entry on the command line).
With that extension to your argument, using .a archive
is looking like a good idea. Thanks!
--
John Skaller skaller at users dot sourceforge dot net
signature.asc
Description
On Sat, 2005-07-23 at 17:34 +1000, Ben Finney wrote:
On 23-Jul-2005, skaller wrote:
On Fri, 2005-07-22 at 10:18 +0100, Neil Williams wrote:
Why isn't the object file built from source
It is compiled to save time.
Save whose time? People who want precompiled binaries will get them
from
On Sun, 2005-07-24 at 22:25 +0100, Neil Williams wrote:
On Sunday 24 July 2005 7:55 pm, skaller wrote:
I'm talking about the binary package(s).
Don't forget that Debian is on so many different platforms, compiling the
main.o on one platform is simply not going to work on others.
I must
the
file is going in one place but being looked for
in the other .. and that just doesn't work :)
--
John Skaller skaller at users dot sourceforge dot net
signature.asc
Description: This is a digitally signed message part
On Fri, 2005-07-22 at 10:18 +0100, Neil Williams wrote:
On Friday 22 July 2005 6:44 am, skaller wrote:
Where should a required object file be put?
Why isn't the object file built from source or implemented as a shared
library?
It is compiled to save time. It isn't a shared library
On Fri, 2005-07-22 at 23:55 +0200, Bas Wijnen wrote:
On Fri, Jul 22, 2005 at 03:44:05PM +1000, skaller wrote:
Where should a required object file be put?
File in question is a mainline stub, associated with a
static archive, program is built by linking it with
the archive and user
Where should a required object file be put?
File in question is a mainline stub, associated with a
static archive, program is built by linking it with
the archive and user object file.
The archive is in /usr/lib, should the .o go there too?
--
John Skaller skaller at users dot sourceforge
.. hmm .. and understanding the languages is just the start.
Heck, I don't understand it all .. and I wrote most of it :)
--
John Skaller skaller at users dot sourceforge dot net
signature.asc
Description: This is a digitally signed message part
On Fri, 2005-07-15 at 19:23 -0700, Michael K. Edwards wrote:
On 7/15/05, skaller [EMAIL PROTECTED] wrote:
Oh .. which DD can be responsible for my package Felix then?
They would have to know:
* C/C++
* OCaml
* Python
* Bash
* Interscript
* Felix
* ocamllex/ocamlyacc
On Thu, 2005-07-14 at 01:25 -0400, kamaraju kusumanchi wrote:
I am trying to package fortranposix library. I produced some debian
packages but I am not satisfied with their quality. For example, when I do
$lintian -i libfortranposix0_0.1-1_i386.deb
E: libfortranposix0:
On Thu, 2005-07-14 at 01:53 -0400, kamaraju kusumanchi wrote:
section 8.1 of debian-policy states that
[sic]The run-time library package should include the symbolic link that
|ldconfig| would create for the shared libraries. [sic]
Does not this mean that ldconfig creates the symbolic
Second call: can someone sponsor my package please?
Hi, I'm seeking a sponsor for Felix (I am
both the packager and upstream author):
* Package Name : felix
Version: 1.1.0
Upstream Author: john skaller[EMAIL PROTECTED]
* URL: http://felix.sourceforge.net
* License
On Sun, 2005-07-10 at 19:54 +0100, Mark Seaborn wrote:
I'm looking for a sponsor for my project, Plash.
Wow, I have to say this sounds very interesting,
I hope someone sponsors it.
--
John Skaller skaller at users dot sourceforge dot net
Download Felix: http://felix.sf.net
signature.asc
On Fri, 2005-07-08 at 13:50 +0530, Y Giridhar Appaji Nag wrote:
On 05/07/08 15:50 +1000, John Skaller said ...
What I am asking for is:
apt-get install fred
and it installs fred. If 'fred' is not available for my architecture,
it is compiled and installed automatically
On Thu, 2005-07-07 at 19:56 +0200, Geert Stappers wrote:
So, you are worried.
Worried about not being i386 enough.
I say: Screw i386 !
Fine to say that, but Ubuntu is screaming ahead of Debian
here -- they actually support amd64, Debian doesn't.
--
John Skaller skaller at users dot
tools can't build from source
The latter is exceptionally annoying (which I consider
a very polite form of what I'd like to actually say ;)
Is there a tool which does that?
I use Synaptic GUI tool, it would be nice if a tool
like that could build from source transparently.
--
John Skaller skaller
On Fri, 2005-07-08 at 12:58 +1000, Ben Finney wrote:
On 08-Jul-2005, John Skaller wrote:
On Thu, 2005-07-07 at 21:27 +0200, Christoph Haas wrote:
You may as well use the http://mentors.debian.net service to
upload your work. It will take care of your files and make them
publicly
Hi, I'm seeking a sponsor for Felix (I am
both the packager and upstream author):
* Package Name : felix
Version: 1.1.0
Upstream Author: john skaller[EMAIL PROTECTED]
* URL: http://felix.sourceforge.net
* License: BSD
* Description: high performance
,
and then the build interaction cannot be cyclic.
Otherwise, if you have a cyclic process in the build,
then there is no alternative than to provide an initial
value for it, hopefully one such that the recursion
fixes fairly quickly ..
BTW: is this vbccz you're talking about?
--
John Skaller
I am seeking some input on the state of the following package:
Package Name: felix
Version: 1.1.0
Upstream author: John Skaller [EMAIL PROTECTED]
Licence: BSD
Description: high performance programming language translator and tools
Source and amd64 binaries can be found at:
http://felix.sf.net
). As a rule of thumb, if your tail
functions have fewer than 9 arguments, you're safe.
The bug is fixed in the CVS repository, 3.08 bug-fix branch.
- Xavier Leroy
---
--
John Skaller, skaller at users.sf.net
PO Box 401 Glebe, NSW 2037, Australia
it will
do so faster, however that package is not available
on all architectures.
This isn't an essential feature, but here is a case,
possibly isolated, where it could be useful.
[There is a related problem, see next email please]
--
John Skaller, skaller at users.sf.net
PO Box 401 Glebe, NSW
Skaller, skaller at users.sf.net
PO Box 401 Glebe, NSW 2037, Australia Ph:61-2-96600850
Download Felix here: http://felix.sf.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Sun, 2005-06-12 at 10:30 +0200, Pierre Habouzit wrote:
Le Dim 12 Juin 2005 08:51, John Skaller a crit :
How should a package build script cope with a fault
in a package used in a build?
The situation: there is a fatal bug in the 'ocaml' binary
package for the amd64 architecture
this on an Ubuntu system? I tried to run
pbuilder but it doesn't work out of the box:
[EMAIL PROTECTED]:/home/skaller # pbuilder create
W: /root/.pbuilderrc does not exist
Distribution is sid.
Building the build environment
- running debootstrap
I: Retrieving debootstrap.invalid_dists_sid_Release
E: Invalid
linkage
and libflx_dynamic.so for compile time linkage. Hope that is right.
2) I seem to have:
dpkg-buildpackage: full upload; Debian-native package (full source is
included)
I hope that is right too ..
--
John Skaller, skaller at users.sf.net
PO Box 401 Glebe, NSW 2037, Australia Ph:61-2-96600850
, flags 0x0150:
HAS_SYMS, DYNAMIC, D_PAGED
start address 0x00023350
--
John Skaller, skaller at users.sf.net
PO Box 401 Glebe, NSW 2037, Australia Ph:61-2-96600850
Download Felix here: http://felix.sf.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe
,
and currently, like Python, Felix writes into the directories
containing sources, but /usr/share/* .. should be read only.
[Yes, this is a bug in my system, it needs to be fixed, but
I need to make a Debian package too and that currently has
a higher priority]
--
John Skaller, skaller at users.sf.net
PO Box
personally
in the reply (I don't normally read this list).
[CC'd to debian-ocaml-maint whose members should note
that Felix is an Ocaml *application* not a library
useful to ocaml programmers]
--
John Skaller, skaller at users.sf.net
PO Box 401 Glebe, NSW 2037, Australia Ph:61-2-96600850
On Thu, 2005-05-26 at 21:33 -0400, Roberto C. Sanchez wrote:
On Fri, May 27, 2005 at 10:44:49AM +1000, John Skaller wrote:
Felix is a 'free for any use' open source advanced
Copyright (C) 2004 John Skaller.
Felix is Free For Any Use.
Redistribution and use in source and binary forms
73 matches
Mail list logo
