On Wed, Apr 9, 2008 at 12:25 AM, DJamé Seddah [EMAIL PROTECTED] wrote:
But I don't get it. These are just genuine package created somewhere
in 10.5/ hierarchy
the problem is there're variants for important system package and it's
not easy (possible?) for the end user to track down against
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marco Bonetti wrote:
| On Wed, Apr 9, 2008 at 12:25 AM, DJamé Seddah [EMAIL PROTECTED]
wrote:
| But I don't get it. These are just genuine package created somewhere
| in 10.5/ hierarchy
| the problem is there're variants for important system
Hi list,
I'd like to know where I could upload some (92 meg actually) binaries
i've made today.
here's the list of the packages I'd like to upload
Regards,
Djamé
.//local/injected/binary-darwin-i386/update-packages/rman_3.1-1_darwin-
i386.deb
DJamé Seddah wrote:
Hi list,
I'd like to know where I could upload some (92 meg actually) binaries
i've made today.
here's the list of the packages I'd like to upload
Regards,
Djamé
.//local/injected/binary-darwin-i386/update-packages/rman_3.1-1_darwin-
i386.deb
On 07 Apr 2008, at 23:10, Alexander Hansen wrote:
We don't currently have a mechanism to do this.
At minimum, we would need to check whether contributed binaries don't
have any cross-linking with e.g macports, so that they aren't
immediately broken for users. I don't believe the .deb file
On Apr 7, 2008, at 7:03 PM, Jean-François Mertens wrote:
On 07 Apr 2008, at 23:10, Alexander Hansen wrote:
We don't currently have a mechanism to do this.
At minimum, we would need to check whether contributed binaries don't
have any cross-linking with e.g macports, so that they aren't
