On Wed, Jun 24, 2015 at 11:03 PM, Lawrence Velázquez lar...@macports.org
wrote:
On Jun 24, 2015, at 8:02 PM, Ryan Schmidt ryandes...@macports.org wrote:
On Jun 24, 2015, at 5:10 PM, Christopher Ramos wrote:
Perhaps it would be feasible to employ an agent or daemon that logs
all changes
On 25.06.2015, at 00:10, Christopher Ramos chrisdavidra...@gmail.com wrote:
Macports, like the Mac App Store, is *curated*; it's not the same thing as
going to some fly-by-night website, downloading, and installing willy nilly.
But that’s the crucial thing which you don’t seem to
On Wed, Jun 24, 2015 at 6:10 PM, Christopher Ramos
chrisdavidra...@gmail.com wrote:
Hm, well I understand your point and, while valid, it's not relevant to my
point. For one, I'm not referring to the problem with a user downloading
malicious code or code that does something the user doesn't
On Jun 23, 2015, at 10:03 PM, Christopher D. Ramos wrote:
Yes, that is what I was saying, where, again, by git project, you mean
some software project that just so happens to do its development in a git
repository. The use of git is incidental to the problem.
Heh, I think I finally see
Hm, well I understand your point and, while valid, it's not relevant to my
point. For one, I'm not referring to the problem with a user downloading
malicious code or code that does something the user doesn't understand.
Macports, like the Mac App Store, is *curated*; it's not the same thing as
On Jun 24, 2015, at 2:31 PM, Christopher Ramos chrisdavidra...@gmail.com
wrote:
You can systematically avoid it by letting the operating system's
security do its thing: Don't use superuser privileges to build
software, and don't use them to install unless you know what it's
going to do.
On Jun 24, 2015, at 5:10 PM, Christopher Ramos wrote:
Hm, well I understand your point and, while valid, it's not relevant to my
point. For one, I'm not referring to the problem with a user downloading
malicious code or code that does something the user doesn't understand.
But yes you are.
On Jun 24, 2015, at 8:02 PM, Ryan Schmidt ryandes...@macports.org wrote:
On Jun 24, 2015, at 5:10 PM, Christopher Ramos wrote:
Perhaps it would be feasible to employ an agent or daemon that logs
all changes to a user's installation. That way, if it's ever bungled
by an outside force, the
You can systematically avoid it by letting the operating system's
security do its thing: Don't use superuser privileges to build software,
and don't use them to install unless you know what it's going to do.
Wow, you know, wow. Now you have me wondering if I've gotten too
comfortable using sudo.
On Tue, June 23, 2015 16:53, Brandon Allbery wrote:
On Tue, Jun 23, 2015 at 4:30 PM, Christopher David Ramos
m74z00...@gmail.com wrote:
Still, I think the Macports version of git should have
some mechanism, or some warning -- something -- to warn or prevent
conflicts between Macports and
On 6/23/15 4:53 PM, Brandon Allbery wrote:
On Tue, Jun 23, 2015 at 4:30 PM, Christopher David Ramos
m74z00...@gmail.com mailto:m74z00...@gmail.com wrote:
Still, I think the Macports version of git should have
some mechanism, or some warning -- something -- to warn or prevent
On 6/23/15 4:51 PM, Ryan Schmidt wrote:
On Jun 23, 2015, at 3:30 PM, Christopher David Ramos wrote:
I don't think you understand what Git is.
Git is not a platform by any reasonable definition of the
word. It's a version control system: a tool that allows content
creators (usually
Hiya larryv,
I don't think you understand what Git is.
Git is not a platform by any reasonable definition of the word. It's
a version control system: a tool that allows content creators (usually
software developers) to organize and distribute their work (usually
source code). Git has
On Jun 23, 2015, at 3:30 PM, Christopher David Ramos wrote:
I don't think you understand what Git is.
Git is not a platform by any reasonable definition of the word. It's
a version control system: a tool that allows content creators (usually
software developers) to organize and distribute
Dear everyone (but mostly other developers),
I think this was all just an unfortunate misunderstanding.
What I *believe* happened (but I have no way to know) is that the OP
probably tried to build a project cloned with git. That project
required autotools and failed to build because of the weird
On Jun 23, 2015, at 5:20 PM, Christopher David Ramos m74z00...@gmail.com
wrote:
Please forgive me if what I'm suggesting is not feasible. That said, it was
my understanding that makefiles include instructions on what and where
libraries should be built.
More or less.
If there were a
On Jun 23, 2015, at 2:09 PM, Jeremy Lavergne jer...@lavergne.gotdns.org
wrote:
On Tue, June 23, 2015 16:53, Brandon Allbery wrote:
On Tue, Jun 23, 2015 at 4:30 PM, Christopher David Ramos
m74z00...@gmail.com wrote:
Still, I think the Macports version of git should have
some
On Tue, Jun 23, 2015 at 4:30 PM, Christopher David Ramos
m74z00...@gmail.com wrote:
Still, I think the Macports version of git should have
some mechanism, or some warning -- something -- to warn or prevent
conflicts between Macports and git projects.
Umm, AI much?
Basically you seem to be
On Jun 23, 2015, at 5:09 PM, Jeremy Lavergne jer...@lavergne.gotdns.org
wrote:
If only we tracked what each package installed: we could find all
conflicts before they happen, and we could tell people what packages to
install for a given binary!
oh, you mean like contents list?
On Tue, Jun 23, 2015 at 11:20 PM, Christopher David Ramos wrote:
Please forgive me if what I'm suggesting is not feasible. That said, it
was my understanding that makefiles include instructions on what and
where libraries should be built.
Yes.
If there were a special Macports
version of
Yes, that is what I was saying, where, again, by git project, you mean
some software project that just so happens to do its development in a git
repository. The use of git is incidental to the problem.
Heh, I think I finally see where we are talking pass one another. I
wholeheartedly agree
On Jun 23, 2015, at 11:03 PM, Christopher D. Ramos
chrisdavidra...@gmail.com wrote:
That said, I don't think it's merely incidental.
I assure you that it is.
After all, git is, in a sense, part of the Macports ecosystem by
virtue of a version of it being hosted by Macports. Is there not
a
On Jun 23, 2015, at 6:01 PM, Jeremy Lavergne jer...@lavergne.gotdns.org
wrote:
Goodness that appeared terrifyingly manual.
yes, I believe it predates the destroot support in MacPorts (that change
happened right around the time I first started paying attention to the project
IIRC, so I don’t
Goodness that appeared terrifyingly manual.
Now that we have buildbots, I'd hope we consider letting them come up with
this as an infrastructure matter.
On Tue, June 23, 2015 17:28, Daniel J. Luke wrote:
oh, you mean like contents list?
On Jun 23, 2015, at 4:13 PM, Christopher David Ramos wrote:
There is no inherent conflict between MacPorts and any given
software downloaded with git. Rather, there is (apparently, from what
you've told us) a conflict between MacPorts and the specific software
you downloaded with git,
Moving this to macports-users, as it's quite off-topic for the ticket.
You may have to subscribe to the list to respond.
https://trac.macports.org/wiki/MailingLists
On Jun 19, 2015, at 3:59 PM, MacPorts nore...@macports.org wrote:
#47755: Broken symlink left by select code when selected port
26 matches
Mail list logo
