Re: multiarch and pkg-config

2010-02-05 Thread Tollef Fog Heen
]] Hendrik Sattler 

Please don't send me copies, I'm subscribed and set my mail-followup-to
as well as mail-copies-to.

| Am Dienstag 02 Februar 2010 21:43:21 schrieb Tollef Fog Heen:
| > ]] Hendrik Sattler

| > | pkg-config actually does support relocation of the libraries but for a
| > | strange reason only on Windows. That means that for cross-compiling,
| > | you have to fixup all paths it returns. The patch would be trivial.
| > 
| > Uhm, no.  You make sure the generated .pc files are correct and it will
| > Just Work.
| 
| The keyword here is _relocatable_
| With a hard-coded 'prefix', there is no "correct".

There's no way to generally support relocatable libraries and it's not
something I'm interested in supporting, particularly not inside Debian.
Just generate .pc files with the right prefix and you're good.

| > | The undocumented "pcfiledir" variable can be used to hack around it,
| > | probably better to convinve upstream to make pkg-config more
| > | cross-compile-friendly. Thus, it may be possible to a generic shell
| > | script as cross-pkg-config wrapper that does what you want (with many
| > | symlinks to make autotools happy).
| > 
| > Feel free to try to convince me.

| #!/bin/sh
| 
| #find the GNU prefix
| GNU_PREFIX=`basename $0 | sed -e 's/\(.*\)-pkg-config/\\1/'`
| 
| #set the new search path for pkg-config
| PKG_CONFIG_LIBDIR="/usr/lib/$GNU_PREFIX/pkgconfig:$PKG_CONFIG_LIBDIR"
| export PKG_CONFIG_LIBDIR

This bit is fairly reasonable.

| #get the location of the .pc file
| PC_NONOPTS=`echo $@ | sed -e 's/\(--[^ ]* \)*//g'`
| PC_FILEDIR=`pkg-config --variable=pcfiledir "$PC_NONOPTS"`
| PC_RESULT=$?
| test "$PC_FILEDIR" || exit $PC_RESULT

This one is not, it won't work at all.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#568501: ITP: doctrine -- PHP Object Relational Mapper

2010-02-05 Thread Federico Gimenez Nieto
Package: wnpp
Severity: wishlist
Owner: Federico Gimenez Nieto 


* Package name: doctrine
  Version : 1.2.1
  Upstream Author : Jonathan H. Wage  
* URL : http://www.doctrine-project.org/
* License : LGPL
  Programming Lang: PHP
  Description : PHP Object Relational Mapper

Doctrine is an object relational mapper (ORM) for PHP 5.2.3+ 
that sits on top of a powerful database abstraction layer (DBAL). 

One of its key features is the option to write database queries 
in a proprietary object oriented SQL dialect called Doctrine Query 
Language (DQL), inspired by Hibernates HQL. This provides developers 
with a powerful alternative to SQL that maintains flexibility without 
requiring unnecessary code duplication.



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Re: why are the watchdog drivers blacklisted?

2010-02-05 Thread Petter Reinholdtsen

[Marco d'Itri]
> I maintain the package providing it, but I fear it is the result of
> cargo cult sysadmining.  A driver will not engage the watchdog
> anyway until /dev/watchdog is opened.

If I remember correctly, the reason is that the observed behaviour is
that a driver sometimes will engage the watchdog without /dev/watchdog
is opened, triggered by one driver starting without anyone touching
/dev/watchdog.  This caused the installer to stop after 1 minute.  I
do not remember any more details.  This was discovered a few years
ago, and I hope that crazy driver has been fixed in the mean time.

Happy hacking,
-- 
Petter Reinholdtsen


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Re: why are the watchdog drivers blacklisted?

2010-02-05 Thread Mark Brown
On Fri, Feb 05, 2010 at 10:11:25AM +0100, Petter Reinholdtsen wrote:
> [Marco d'Itri]

> > I maintain the package providing it, but I fear it is the result of
> > cargo cult sysadmining.  A driver will not engage the watchdog
> > anyway until /dev/watchdog is opened.

> If I remember correctly, the reason is that the observed behaviour is
> that a driver sometimes will engage the watchdog without /dev/watchdog
> is opened, triggered by one driver starting without anyone touching
> /dev/watchdog.  This caused the installer to stop after 1 minute.  I
> do not remember any more details.  This was discovered a few years
> ago, and I hope that crazy driver has been fixed in the mean time.

That's just a buggy watchdog driver, though (unless the problem was
really that the watchdog was already enabled by the hardware prior to
startup, but then not loading the driver isn't going to help anything).


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Re: why are the watchdog drivers blacklisted?

2010-02-05 Thread Frans Pop
Petter Reinholdtsen wrote:
> This caused the installer to stop after 1 minute.

Not sure how this could have affected the installer as we don't include any 
watchdog modules in D-I (at least, not that I'm aware of).

Cheers,
FJP


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Re: why are the watchdog drivers blacklisted?

2010-02-05 Thread Marco d'Itri
On Feb 05, Petter Reinholdtsen  wrote:

> do not remember any more details.  This was discovered a few years
> ago, and I hope that crazy driver has been fixed in the mean time.
So it looks like this *is* my fault, in my defense I can only say that I
got bad advice from the kernel maintainers...
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=249600

I cannot even find anymore this i810_tco/i8xx_tco module, so in the next
udev upload I will remove all watchdog drivers from the blacklist and
maybe add back the ones reported as broken.

-- 
ciao,
Marco


signature.asc
Description: Digital signature


Bug#568530: ITP: campcaster -- A radio program automation and support tool

2010-02-05 Thread Alessio Treglia
Package: wnpp
Severity: wishlist
Owner: Alessio Treglia 

* Package name: campcaster
  Version : 1.3.0
  Upstream Author : Media Developmnet Loan Fund, http://www.mdlf.org/
* URL : http://campcaster.campware.org
* License : GPL
  Programming Lang: C++
  Description : A radio program automation and support tool

 Campcaster is the first free and open radio management software that 
 provides live studio broadcast capabilities as well as remote automation
 in one integrated system.
 .
 Major features of Campcaster: live, in-studio playout; web-based remote
 station management; automation; playlists; centralized archives of station
 program material; solid, fast playback using the Gstreamer multimedia
 framework; search-based backup; localization into several languages;
 innovative design by the Parsons School of Design; open, extensible
 architecture based on XML-RPC.



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Re: multiarch and pkg-config

2010-02-05 Thread Hendrik Sattler
Am Freitag 05 Februar 2010 09:04:45 schrieb Tollef Fog Heen:
> | #get the location of the .pc file
> | PC_NONOPTS=`echo $@ | sed -e 's/\(--[^ ]* \)*//g'`
> | PC_FILEDIR=`pkg-config --variable=pcfiledir "$PC_NONOPTS"`
> | PC_RESULT=$?
> | test "$PC_FILEDIR" || exit $PC_RESULT
> 
> This one is not, it won't work at all.
> 

It does, at least for my use-case of pkg-config.

Though I agree that this is not needed for you (only for relocation of 
libraries). But still, one simple wrapper is enough to support multiarch 
library dirs.

HS


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Re: multiarch and pkg-config

2010-02-05 Thread Peter Samuelson

[Goswin von Brederlow]
> Then installing the i386 package on amd64 would create the symlink
> and make sources building for 64bit find the 32bit libraries. Verry
> bad idea.

1) People shouldn't be installing -dev packages from the wrong
architecture.  It is too early in the game to rely on that sort of
thing yet.

2) If some source package does not express a Build-Depends in such a
way as to cause the correct architecture "foo-dev" package to be
installed, I'd say that's a serious bug in either the source package,
or the multi-arch design.

3) The dh_makeshlibs postinst logic _could_ only create the symlink if
the architecture is the host architecture, however you detect that in
multi-arch land.  And indeed it could stop doing so if it detects that
pkg-config is an appropriate version.
-- 
Peter Samuelson | org-tld!p12n!peter | http://p12n.org/


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Re: multiarch and pkg-config

2010-02-05 Thread Josselin Mouette
Le mercredi 03 février 2010 à 10:48 +0100, Goswin von Brederlow a
écrit : 
> > If we want to support multiarch compilation, this sounds ok to me.  I'm
> > personally not convinced by the point of doing it.  Though.
> 
> We probably don't want multiarch compilation as such but cross
> compilation is a huge benfit for many people and multiarch dev packages
> would make it possible to cross compile without having to set a sysroot
> and without mangling packages during unpacking.

Cross-compiling packages without a dedicated build root sounds like a
very, very bad idea to me.

> It also makes sense to compile sources with everything in the triplet
> dir. No point having the *.so link or .pc files in different libdirs. It
> is probably harder to not multiarchify the -dev packages as well.

It is only marginally harder to make the .so symlink point to the .so.N
in the arch-triplet directory. It is just the same as what is done
with /lib.

-- 
 .''`.  Josselin Mouette
: :' :
`. `'   “I recommend you to learn English in hope that you in
  `- future understand things”  -- Jörg Schilling


signature.asc
Description: Ceci est une partie de message numériquement signée


Bug#568598: ITP: librt-java -- runtime routines for projects of intarsys

2010-02-05 Thread Steffen Möller
Package: wnpp
Severity: wishlist
Owner: "Steffen Möller" 

* Package name: librt-java
  Version : 4.7
* URL : 
http://opensource.intarsys.de/home/en/index.php?n=JPodRenderer.DevelopersGuide
* License : GPL-3+
  Programming Lang: Java
  Description : runtime routines for projects of intarsys

The isrt.jar, also isRuntime, the basic runtime library used within all 
intarsys projects.
The latter are contributing to the handling of PDFs and a dependency of later 
versions of PDFsam.



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#568602: ITP: libgpars-groovy-java -- open-source concurrency library for Groovy

2010-02-05 Thread Miguel Landaeta
Package: wnpp
Severity: wishlist
Owner: Miguel Landaeta 

* Package name: libgpars-groovy-java
  Version : 0.9
  Upstream Author : Vaclav Pech 
* URL : http://gpars.codehaus.org/
* License : Apache-2.0
  Programming Lang: Groovy, Java
  Description : open-source concurrency library for Groovy

Library that provides multiple high-level abstractions for
writing concurrent code in Groovy, including: map/reduce,
fork/join, asynchronous closures, actors, agents, dataflow
concurrency and other concepts.



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org