Hi,
I'm a long-time Fink user, but I don't know how I have to commit a new
package. I have made an info and a patch file for the network tool
hping and I have included them here. What's the next thing I have to
do? I'm interested in committing more Fink packages.
Regards,
Koen Vervloesem
--
"
Koen Vervloesem
--
"Which is worse: ignorance or apathy? Who knows? Who cares?"
hping.info
Description: Binary data
hping.patch
Description: Binary data
On Wed, 10 Dec 2003, Koen Vervloesem wrote:
> Hi,
>
> I'm a long-time Fink user, but I don't know how I have to commit a new
> package. I have made an info and a patch file for the network tool
> hping and I have included them here. What's the next thing I have to
> do? I'm interested in committin
I'm writing a package for libxml++, and it has the strange particularity
that the package won't compile if there is an older version of libxml++
present on the system.
This is due to the building of tests with both link flags :
-L/sw/lib -L../../libxml++/.libs
This has a bad consequence because it
Olivier Bonnet wrote:
I'm writing a package for libxml++, and it has the strange particularity
that the package won't compile if there is an older version of libxml++
present on the system.
This is due to the building of tests with both link flags :
-L/sw/lib -L../../libxml++/.libs
This has a bad
Le 10 déc. 2003, à 18:15, Benjamin Reed a écrit :
generally you get things like this with the default LDFLAGS from fink
packages. You could try:
NoSetLDFLAGS: true
SetLIBS: -L%p/lib
...that might make it so the /sw/lib ends up after the other.
Otherwise, you might have to hack the Makefile (we
On Tue, Dec 09, 2003 at 06:36:45PM -0500, David R. Morrison wrote:
> Folks, we need a few updates in the packaging manual.
%% isn't documented in Section 2.2 (hello, thesin?).
> Also, I detected some amiguities between Validation.pm and what the manual
> says, concerning the fields in a SplitOff.
I haven't looked at the code or tested, but Type: perl in a split is
useless as type is for the buildprocess, splits aren't used till
install phase.
on the other hand updatePOD should be avail to splits but updatePOD now
uses type perl for the version. sorta chicken and the egg. so really
Ty
there are a few discrepancies with this, in some functions it's
inherited like in the dep engine, but in others like remove it's not.
The reason for this is unknown to me, though I do believe it shouldn't
be inherited at all. It maybe have been this way for bootstrapping?
when i re wrote the
Depending on the approach when programming, documentation can easily
come before a feature exists.
Generically, some methods involve first writing a short description of
what is to be done. Then a flowchart is made by referencing the
description, and sometimes the flowchart is much more detaile
Perhaps in a splitoff Type should be inheirited and a new _is_splitoff
key should be added (and decisions that used to be based on whether
_type=>splitoff would now look for _is_splitoff instead). I'm
currently hacking the Type processing code that does magical things
with 'perl' (branch type_langv
On Wed, Dec 10, 2003 at 02:09:56PM -0500, Daniel Macks wrote:
> On Tue, Dec 09, 2003 at 06:36:45PM -0500, David R. Morrison wrote:
> > Folks, we need a few updates in the packaging manual.
>
> %% isn't documented in Section 2.2 (hello, thesin?).
Okay, I just did this in CVS (including a note that
if the next release is 0.18.0 :)
---
TS
http://southofheaven.org
Chaos is the beginning and end, try dealing with the rest.
On 10-Dec-03, at 8:30 PM, Daniel Macks wrote:
On Wed, Dec 10, 2003 at 02:09:56PM -0500, Daniel Macks wrote:
On Tue, Dec 09, 2003 at 06:36:45PM -0500, David R. Morrison wrote:
well pkgs with updatepod in a splitoff wouldn't be a pm, it's be
something like net-snmp or a pkg with a perlmodule, now I'd rather
split this into two info files, not everyone has taken that approach.
---
TS
http://southofheaven.org
Chaos is the beginning and end, try dealing with the rest.
On
14 matches
Mail list logo
