Skip to content

For your consideration: edge case regarding package name #133

@nevotheless

Description

@nevotheless

I will just post this here, well knowing it's probably way to little of an issue to change anything but i want to make my case clear anyways.

Today i encountered an potential for month / years undiscovered issue because of the name of the composer dependency wikimedia/less.php.

We are building a rather big software and have a mechanism to build our update packages using rsync for example to make use of filters and include/excludes.

In this particular case we're copying over all files expect php files because they are getting handled a different way.

A dummy rsync command for this looks like this

rsync -av --links --quiet ./vendor/ ./dst/ --exclude='*.php'   --exclude='*.inc'

Today is discovered this and of course this command did all our composer dependencies over EXCEPT for wikimedia/less.php because of how the package / folder is named.

We solved this easily but i fear the package name in itself has potential for more easy to miss issues for other projects in the future.

🥳 Thanks for reading.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions