Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Ben Johnson
    @cbj4074
    @manju16832003 I have no idea why it takes so much time, but that is a separate issue.
    The error you're receiving now is pretty cut-and-dry. You need PHP 7.1.3 or later to use the packages you're requesting.
    Manjunath Reddy
    @manjufy
    Interesting.
    Ben Johnson
    @cbj4074
    It likely has something to do with pcntl, which is available only in 7.1.
    So, you either need to use older versions of everything, or upgrade PHP.
    Manjunath Reddy
    @manjufy
    is there a command to upgrade php to latest..
    Ben Johnson
    @cbj4074
    Yeah, it looks like you are using Ondrej Sury's PPA for Ubuntu. Smart guy!
    Is this in a VM? Is it testing only? Do you care about anything breaking?
    Manjunath Reddy
    @manjufy
    oh Yes...
    Homestead vagrant from Laravel
    Ben Johnson
    @cbj4074
    Okay, perfect. Then the easiest thing to do is simply to upgrade Homestead.
    Your version appears to be quite stale.
    Manjunath Reddy
    @manjufy
    Yes, I guess so. ... my vagrant box is quite old... Probably 1.3 years lol
    Ben Johnson
    @cbj4074
    That's a different subject, though, and may be best asked over in laravel/laravel.
    (I can help you there)
    Kongthap Thammachat
    @jeud

    hi i would like to install private repo from github instead of packagist, i have setup my composer.json as below

    {
      "repositories": [
        {
          "type": "package",
          "package": {
            "name": "laravel-repo",
            "version": "1.1",
            "source": {
              "url": "https://github.com/jeud/laravel-repo.git",
              "type": "git",
              "reference": "master"
            }
          }
        }
      ],
      "require": {
        "laravel-repo": "1.1"
      }
    }

    it's working but i'm not sure what different between defining type: packageinside repositories and type: git without type: package ?

    shilili
    @shilili
    Hi all! Anyone interested in participating in a php authentication research project? It's remote and we're paying developers $100/hr to participate. The goal is to get insights on how to improve the developer onboarding experience for a SaaS. Message me if interested!
    ahsan waseem
    @ahsanwaseem
    hi everyone
    need a little help
    regarding php
    Diego Gullo
    @bizmate
    @jeud it is all pretty much explained here. https://getcomposer.org/doc/02-libraries.md#publishing-to-a-vcs
    @jeud type package is if you want to import the project without relying on a composer.json existing on the package source. In general it is best to have a composer.json on that repository if you control it and then just use vcs as a type
    Can anyone help with this conflict issue? composer/composer#7089 I have no understanding of what it means. Ie why is it complaining about a root package or something?
    Diego Gullo
    @bizmate
    @manju16832003 remove the double require
    Robert Main
    @robertmain
    Hey guys
    Anyone know off-hand how to have Composer load a single file?
    i.e: require the PHP file and instantiate the class contained therein?
    Owen Melbourne
    @OwenMelbz
    it can load a single file yes, but it wont execute any code
    Joaquin Varela
    @jjvvx
    Hi. I have a project that I want to upload outside of Packagist. I've just one question: where does Composer get the vendor and package name when not using public Packagist? Does it use the explicit definition in composer.json or does something external influence that?
    Owen Melbourne
    @OwenMelbz
    that completly depends, you get different repo types, zip, packages, composer, vcs
    so if you setup a composer repo - like satis, then it uses the composer.json
    if you using a git repo - then you define a custom name in the projects composer.json rather than the 3rd party package
    Joaquin Varela
    @jjvvx
    ah I see
    Karl Viiburg
    @kurbar

    Hi. I'm developing a modular application on Composer and have a question regarding dependency inclusions during development.

    Currently I have the packages pulled from a VCS.

    I have a core module which requires all other modules.

    When developing the different modules, I would like to pull in the core module as it implements the user logic.

    Though the problem is that when I require-dev the core module, then it tries to automatically install it's dependencies for the modules as well, causing a recursion: e.g help-module > core > help-module...

    Does Composer offer any possibilities to pull in a dev dependency without installing the sub-dependencies?

    Romain GRELET
    @babaorum
    It doesn't feel right having your core module requiring all modules.
    It should be suggested packages I think.
    Karl Viiburg
    @kurbar
    The core is sort of like the base on top of which other modules are built upon
    Or should I have a separate app package that pulls together all the modules including core?
    Romain GRELET
    @babaorum
    Yes i understand. But in your project. You should not say i need the "core" library. You should say, I need the featureXx library (and this library will require the core library to work).
    If you want some king of install with all modules without requiring them all in each project you do, it may be done in a different project dedicated to forming it all.
    Romain GRELET
    @babaorum
    Maybe look at some php framework like symfony, which are splitting into components, and only requiring the needed part in each one.
    Karl Viiburg
    @kurbar

    I took laravel/framework as a basis for mine. which yeah basically is the same structure that Symfony follows.

    I do see that laravel makes use of the replace keyword for replacing individual subpackages, but based on the docs I'm not 100% sure if this is a necessary thing for me as well.

    Though yes a difference is that laravel supplies a separate laravel/app package which requires the laravel/framework (core) package.

    So maybe I will get away by using replace?

    Romain GRELET
    @babaorum
    Yes the replace keywork could be usefull. But are you sure it is the right move for you're core package to require you other packages ? Specially all of them ?
    Owen Melbourne
    @OwenMelbz
    anybody know if/how you can overwrite a dependencies package type? e.g one of the packages i want to pull in, is defined as "type": "wordpress-plugin"but I need it to install into the vendor like a normal "type": "library" is there anything i can do to overwrite it locally?
    Varulv
    @Varulv1997
    FHRITP
    Nikita
    @xenmayer
    somebody knows how to prevent symlinking local package by composer create-project?
    p.s. I have created github issue composer/composer#7274 with more comprehensive explaining
    Ruslan Kvashuk
    @rossanoua
    Hi all!
    Any russian/ucrainian speaking?
    i have a little trouble
    i’m not sure if it’s going as expected
    i was executed command composer require “vendor/pakage"