Hi,
it is quite worth to understand the way apt works and being able to use
it more than just fetching packages. So thanks for this email.
The only issue is the variance among systems using different package
management. But this can be solved using as much as possible the same
dist, apart of specific uses (e.g. Oracle Linux for Oracle software )
that will not require any big effort in this type of task.
I still prefer the system stopping at the boundary of perl, and at the
boundary in general. It worked up to 11.04 so the decision to depart of
using apt to put things where they could be in other ways is both
respectful and questionable. One should be free once the system is ready
to build, using the apt to provide the environment, to:
-> set the end packages from apt
-> set the software from source
This is the real point of this story.
Meanwhile I have dismissed the VM for now and will be back sometime
later this year (or the next) . About the errors I got, that was about
the same described.
Fabio D'Alfonso
'Enabling Business Through IT'
cell. +39.348.059.40.22 ***
web: www.fabiodalfonso.com <http://www.fabiodalfonso.com/>
email: [email protected]
<mailto:[email protected]>linkedin:
www.linkedin.com/in/fabiodalfonso <http://it.linkedin.com/in/fabiodalfonso>
twitter: www.twitter.com/#!/fabio_dalfonso
<http://www.twitter.com/#%21/fabio_dalfonso>
fax: +39.06.874.599.581
BlackBerry® Wireless Enabled Address.
** Hidden numbers are automatically rejected by the phone*
On 4/22/2013 9:35 AM, Dima Kogan wrote:
Clifford Sobchuk <[email protected]> writes:
Hi Dima, That is the way I have always upgraded. When I try to
initially install via cpan it always fails. I install via apt, then I
use CPAN to upgrade. I now see what you mean about the two different
directories for the two versions - apt puts it in /usr/lib/perl5 where
as cpan puts it into /usr/local/lib/perl/5.14.2/PDL I don't develop
PDL, I only use PDL in my scripts. I haven't run into any problems
previously - apparently I have been lucky.
Ok. That's interesting. I suspect what's happening is that when you ask
APT to install PDL, it installs not just PDL, but its dependencies also
(as it should). And it is these dependencies that make the CPAN
installation work. Installing PDL via cpan SHOULD fail if there are
missing dependencies. And in a nutshell, this is why you should always
use APT instead of other tools: it knows about dependencies, while tools
such as cpan do not.
Since all you are trying to do is to install a newer PDL, by far the
best thing you can do is to simply build a new package, and install it.
The PDL sources already have the debianization in them, so this is easy
and painless (just tried it).
Steps:
1. You need to bump the version of the debian package. This entails
creating a new entry in debian/changelog. You can do this yourself, or
you can apply the attached patch (do not commit it; it's just for your
personal package).
2. Make sure your checkout is fresh and clean. 'git reset --hard' and
'git clean -ffdx' is what I generally do. Note that this will delete
existing files.
3. Build the package! From the PDL directory do
dpkg-buildpackage -us -uc -b
This asks the machine to build the package without signing anything and
without building the sources. This will build a fresh .deb in ..
4. Install it. 'dpkg -i ../pdl_2.6.0~1-1_amd64.deb'
I just tried it on my Debian/sid system; worked fine. Note that if you
have stuff installed via the cpan utility (existing stuff in
/usr/local/lib/perl/...) then these files may confuse the build and/or
tests and it may not work. Having multiple simultaneous installations
such as this is just asking for things to break IMHO.
Let me know if something here doesn't work.
dima
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
