aptly publish switch should be able to figure components from snaps #194

Open
fgsch opened this Issue Feb 7, 2015 · 5 comments

Comments

Projects
None yet
3 participants
@fgsch

fgsch commented Feb 7, 2015

To be consistent with aptly publish snapshot, aptly publish switch should support figuring out the component names from the snapshots when invoked as, e.g. -component=, distro prefix snap1 snap2.

@smira

This comment has been minimized.

Show comment
Hide comment
@smira

smira Feb 19, 2015

Member

Should it take component names from snapshots or accept components in the order specified when aptly publish snapshot was called?

Member

smira commented Feb 19, 2015

Should it take component names from snapshots or accept components in the order specified when aptly publish snapshot was called?

@smira smira added the enhancement label Feb 19, 2015

@smira smira added this to the v0.9.5 milestone Feb 19, 2015

@fgsch

This comment has been minimized.

Show comment
Hide comment
@fgsch

fgsch Feb 20, 2015

I reckon from the snapshots in case you want to add components that were not originally there - is that possible, right?

fgsch commented Feb 20, 2015

I reckon from the snapshots in case you want to add components that were not originally there - is that possible, right?

@smira

This comment has been minimized.

Show comment
Hide comment
@smira

smira Feb 20, 2015

Member

Currently you can't change list of components during aptly publish switch, so these would be the same components as specified while doing aptly publish snapshot. You might update only some components, but you can't add new or remove old ones.

Member

smira commented Feb 20, 2015

Currently you can't change list of components during aptly publish switch, so these would be the same components as specified while doing aptly publish snapshot. You might update only some components, but you can't add new or remove old ones.

@fgsch

This comment has been minimized.

Show comment
Hide comment
@fgsch

fgsch Feb 20, 2015

Ok, even so I'd prefer to use the ones from the supplied snapshot in case this limitation change in the future.

fgsch commented Feb 20, 2015

Ok, even so I'd prefer to use the ones from the supplied snapshot in case this limitation change in the future.

@oCCtet

This comment has been minimized.

Show comment
Hide comment
@oCCtet

oCCtet Feb 21, 2015

Since the aptly publish snapshot -component=, snap1 snap2 takes the component names from the snapshots, it would be logical that aptly publish switch could do the same.

However, one can rename the components during initial publish via aptly publish snapshot -component=master,non-free main-snap restricted-snap. Does aptly keep track of this? If not, aptly publish switch should error out if any snapshot given contains un-published component name.

oCCtet commented Feb 21, 2015

Since the aptly publish snapshot -component=, snap1 snap2 takes the component names from the snapshots, it would be logical that aptly publish switch could do the same.

However, one can rename the components during initial publish via aptly publish snapshot -component=master,non-free main-snap restricted-snap. Does aptly keep track of this? If not, aptly publish switch should error out if any snapshot given contains un-published component name.

@smira smira modified the milestones: v0.9.5, v0.9.6 Mar 13, 2015

@smira smira modified the milestones: v0.9.6, v0.9.7 Jan 24, 2016

@smira smira modified the milestones: v0.9.7, v0.9.8 Apr 18, 2016

@smira smira removed this from the v0.9.8 milestone Mar 27, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment