On Apr 15, 2011, at 08:07, p...@macports.org wrote:
> Revision: 77874
> http://trac.macports.org/changeset/77874
> Author: p...@macports.org
> Date: 2011-04-15 06:07:58 -0700 (Fri, 15 Apr 2011)
> Log Message:
> ---
> new port: objectmarker
>
> Added Paths:
> ---
>
On 2011-4-16 00:59 , Andrea D'Amore wrote:
> On Fri, Apr 15, 2011 at 12:50 PM, Anders F Björklund
> wrote:
>> It already compares versions ? If the user had done a "port sync", he would
>> have seen the newer version.
>
> Btw, does "sync" action tries to upgrade all repositories?
It syncs all
On Fri, Apr 15, 2011 at 12:50 PM, Anders F Björklund wrote:
> It already compares versions ? If the user had done a "port sync", he would
> have seen the newer version.
Btw, does "sync" action tries to upgrade all repositories?
I was wondering if an user could have a local repository on svn too
On 2011-4-15 21:40 , Ryan Schmidt wrote:
> On Apr 15, 2011, at 06:13, Joshua Root wrote:
>> On 2011-4-15 20:37 , Ryan Schmidt wrote:
>>> By design, if you have a local portfile for a port, then that will be used,
>>> instead of any identically-named port in the main port repository. Some
>>> user
On 2011-4-15 22:12 , Anders F Björklund wrote:
> Another package that seems missing from most Linux distros
> is mtree, so I made some custom rpm/deb packages for that:
>
> http://svn.macports.org/repository/macports/users/afb/mtree-2.7-5.src.rpm
> http://svn.macports.org/repository/macports/users
On 04/15/2011 02:36 PM, Anders F Björklund wrote:
> The instructions to install or uninstall MacPorts are
> usually regarded as almost unreadable, I have heard.
I agree, it's too complicated.
We also have different installation instructions on macports.org, the
wiki and the guide.
Rainer
___
We could add a one-liner just like we do if there's no portindex or it older
than two weeks:
---> local portfile repo detected: some ports will not be updated
Not sure if the second half is what we want to convey but should spook the user
into asking instead of being in the dark indefinitely.
Russell Jones wrote:
> The other reason for platform independence, I guess, is that it helps OS X
> version independence, i.e. with future versions that may drop features MP
> depends on.
It did serve as an attempt to identify all such features:
http://www.macports.org/install.php#other
The o
Arg. I'm not a big GIT user, so thank you for figuring out the branch name.
In r77872, I've gone back to using GIT for fetch using the branch name you
found, and it (again) seems to work. I'm glad I'm the only user for now :) -
MLD
On Apr 15, 2011, at 3:45 AM, Ryan Schmidt wrote:
> On Apr 14
Joshua Root wrote:
> Since some people want to run MacPorts mirrors on Linux,
> I re-added the support for using libcrypto for checksums.
Thanks! I like increased platform-independence. :)
>>>
>>> Make no mistake, MacPorts is still highly platform-dependent,
>>> both by choice
Ryan Schmidt wrote:
>>> If you look at the output in the above ticket, it shows that MacPorts
>>> was aware of php5 @5.3.6 (presumably from the rsync port repository),
>>> but still chose php5 @5.3.5 (presumably from the local directory
>>> which came from an old ports tarball). I think that's the
On Apr 15, 2011, at 06:13, Joshua Root wrote:
> On 2011-4-15 20:37 , Ryan Schmidt wrote:
>> By design, if you have a local portfile for a port, then that will be used,
>> instead of any identically-named port in the main port repository. Some
>> users may have forgotten that they have a local por
On Apr 15, 2011, at 06:06, Rainer Müller wrote:
> On 04/15/2011 01:00 PM, Ryan Schmidt wrote:
>> If you look at the output in the above ticket, it shows that MacPorts
>> was aware of php5 @5.3.6 (presumably from the rsync port repository),
>> but still chose php5 @5.3.5 (presumably from the local
On 2011-4-15 21:07 , Rainer Müller wrote:
> On 04/15/2011 11:29 AM, Anders F Björklund wrote:
>> Ryan Schmidt wrote:
>>
Since some people want to run MacPorts mirrors on Linux,
I re-added the support for using libcrypto for checksums.
>>>
>>> Thanks! I like increased platform-independence
On 2011-4-15 20:37 , Ryan Schmidt wrote:
> By design, if you have a local portfile for a port, then that will be used,
> instead of any identically-named port in the main port repository. Some users
> may have forgotten that they have a local portfile, which can result in a
> problem, as in this
On 04/15/2011 11:29 AM, Anders F Björklund wrote:
> Ryan Schmidt wrote:
>
>>> Since some people want to run MacPorts mirrors on Linux,
>>> I re-added the support for using libcrypto for checksums.
>>
>> Thanks! I like increased platform-independence. :)
>
> Make no mistake, MacPorts is still high
On 04/15/2011 01:00 PM, Ryan Schmidt wrote:
> If you look at the output in the above ticket, it shows that MacPorts
> was aware of php5 @5.3.6 (presumably from the rsync port repository),
> but still chose php5 @5.3.5 (presumably from the local directory
> which came from an old ports tarball). I t
On Apr 15, 2011, at 05:50, Anders F Björklund wrote:
> Ryan Schmidt wrote:
>
>> By design, if you have a local portfile for a port, then that will be used,
>> instead of any identically-named port in the main port repository. Some
>> users may have forgotten that they have a local portfile, wh
Ryan Schmidt wrote:
> By design, if you have a local portfile for a port, then that will be used,
> instead of any identically-named port in the main port repository. Some users
> may have forgotten that they have a local portfile, which can result in a
> problem, as in this situation where the
By design, if you have a local portfile for a port, then that will be used,
instead of any identically-named port in the main port repository. Some users
may have forgotten that they have a local portfile, which can result in a
problem, as in this situation where the user's local port was older
The other reason for platform independence, I guess, is that it helps OS X
version independence, i.e. with future versions that may drop features MP
depends on.
Russell
- Original Message -
From: Anders F Björklund [mailto:a...@macports.org]
Sent: Friday, April 15, 2011 10:29 AM
To: Rya
Ryan Schmidt wrote:
>> Since some people want to run MacPorts mirrors on Linux,
>> I re-added the support for using libcrypto for checksums.
>
> Thanks! I like increased platform-independence. :)
Make no mistake, MacPorts is still highly platform-dependent,
both by choice and by accident. There
On Apr 15, 2011, at 02:46, Anders F Björklund wrote:
> Since some people want to run MacPorts mirrors on Linux,
> I re-added the support for using libcrypto for checksums.
Thanks! I like increased platform-independence. :)
___
macports-dev mailing lis
Since some people want to run MacPorts mirrors on Linux,
I re-added the support for using libcrypto for checksums.
There was also some breakage in the support for FreeBSD,
using an older (1999?) version of libmd, but that's fixed.
For Mac OS X, there are *no* changes. It will still use
CommonCryp
On Apr 14, 2011, at 08:06, Michael Dickens wrote:
> On Apr 14, 2011, at 2:48 AM, Ryan Schmidt wrote:
>> You must lock this fetch to version 003.000.001, using git.branch. Otherwise
>> users installing the port at different times will get different versions of
>> the software (assuming upstream
25 matches
Mail list logo
